There are many configuration options for endpoints using the NServiceBus host. The endpoint configuration specifies levels of logging, subscription, saga storage, and more.
Profiles enable tailoring endpoints configuration for different environments without recompiling code.
There are two categories of profile:
- Environment profiles can be used to avoid common configuration errors that occur when manually moving a system between different environments, e.g. from development to production.
- Feature profiles allow turning NServiceBus features, such as performance counters, on and off with no code changes.
By default, NServiceBus comes with a set of predefined environment and feature profiles. It's also possible to create custom profiles or customize the default profiles; to learn more about those options refer to the NServiceBus host profiles customization article.
There are three built-in environment profiles that adjust the behavior of the host to the environment in which the endpoint is running. These profiles can be used to easily switch between different environments during development, testing, and deployment.
Suitable for running on a development machine, for example, inside Visual Studio.
InMemorypersistence is used for storing information like sagas, subscriptions, timeouts, etc. This is a convenient option for development, but should not be used in production.
- The Lite profile by default turns on the
- Installers are always invoked when running the Lite profile.
- Logging is output to the console.
Suitable for running the endpoint in integration and QA environments.
- Installers are invoked to make deployment easy to automate.
- Logging is output to the console by default.
The default if no explicit profile is defined. This profile configures the endpoint for production use.
- Installers are not invoked since the endpoint is often installed as a Windows Service and does not run with elevated privileges. Installers run only when installing the host or when the code runs inside Visual Studio in Debug mode.
- All configured storage is durable and suitable for scale out.
- Logging is output to a log file in the runtime directory.
- Performance counters are installed by default.
Mastermakes the endpoint a "master node endpoint". This means that it runs the gateway for multi-site interaction, the timeout manager, and the distributor. It also starts a worker that enlists with the distributor. It cannot be combined with the Worker or Distributor profiles.
Workermakes the current endpoint enlist as a worker with its distributor running on the master node. It cannot be combined with the Master or Distributor profiles.
Distributorstarts the endpoint as a distributor only. This means that the endpoint does no work and only distributes the load among its enlisted workers. It cannot be combined with the Master and Worker profiles.
PerformanceCountersturns on the NServiceBus performance counters. Performance counters are enabled by default when running the Production profile.
If the host is run without specifying a profile, NServiceBus defaults to the
To activate a specific profile, pass the full name of the profile in the command line when starting the host. Type names are case-insensitive. Profiles can be combined by separating them with white space.
For example, to run the endpoint with the
.\NServiceBus.Host.exe nservicebus.integration nservicebus.performancecounters
When installing the host as a Windows Service, the profiles used during installation are saved and they are used every time the host starts. In order to install the host with the
.\NServiceBus.Host.exe /install nservicebus.production nservicebus.performancecounters
The built-in profiles use the following logging configurations:
|Production||Rolling File||Configurable, Warn by default|
The rolling file logs are written to the
logfile in the same directory as the executable. The file grows to a maximum size of 1MB, then a new file is created. A maximum of ten files is kept, then the oldest file is erased. If not otherwise specified, the logging threshold is set to the
Warn level. To configure the logging threshold, see changing logging levels.
Refer to the logging configuration article to learn about customizing logging configuration.
The built-in profiles use the following default persistence settings:
|Timeout||In-Memory||RavenDB or as configured||RavenDB or as configured|
|Subscription||In-Memory||RavenDB or as configured||RavenDB or as configured|
|Saga||In-Memory||RavenDB or as configured||RavenDB or as configured|
|Gateway||In-Memory||RavenDB or as configured||RavenDB or as configured|
In the Lite profile, NServiceBus Host will always use the in-memory persistence. In the Integration and Production profiles, the Host verifies if a specific persistence mechanism is provided, e.g. in the endpoint configuration. If not specified otherwise, then RavenDB persistence will be used by default.