By fully-qualified name
dotnet run — wolverine-diagnostics describe-handlers MyApp.Orders.CreateOrderHandler
The argument is matched against the types in your application — exact full name, then exact short name, then
a fuzzy "contains" match. If the term matches **more than one** type, Wolverine prints a discovery report for
*each* match. For every matched type the report shows whether its assembly is being scanned, which type-level
include/exclude rules HIT or MISS, and — for each method — whether it satisfies the handler naming and
signature conventions.
Like the other diagnostics commands, this builds the host and compiles the handler graph but does **not**
start it, so no database or message-broker connections are opened.
## Other Highlights
* See the [code generation support](./codegen)
* The `storage` command helps manage the [durable messaging support](./durability/)
* Wolverine has direct support for [Oakton](https://jasperfx.github.io/oakton) environment checks and resource management that
can be very helpful for Wolverine integrations with message brokers or database servers
---
---
url: /guide/configuration.md
---