Console Logging Configuration
This guide provides the exact .env file parameters required to set up Console logging.
All logging settings are managed directly within your .env configuration file.
Step 1. Set the Log Level
To control the volume of diagnostic data generated by the application, set the global verbosity using the Serilog__MinimumLevel__Default parameter.
The available levels are Information, Debug, Warning, and Error
Warning: Avoid Debug Mode in Production
It is highly recommended to keep the log level set to Errorfor regular day-to-day operations. You should only change this value to Debug if explicitly instructed by Sendent Support to capture detailed diagnostics for bug resolution. The Debug level generates a massive amount of data and can quickly consume disk space and degrade performance.
Step 2. Select the Log Output Destination
The application uses a bitwise mathematical configuration for the Service__LoggingConfiguration__LogsOutput parameter. To enable Console output, you must include the value 1.
Example:
Service__LoggingConfiguration__LogsOutput=1If you wish to combine Console logging with other methods, simply sum their respective values (e.g., 1 for Console + 2 for Database = 3).
Step 3. Accessing Your Logs
Docker Deployment: Open your terminal, navigate to the directory containing your
docker-compose.ymlfile, and run the following command to stream logs in real-time.
docker compose logsBinary Deployment: The logs will be printed directly in the active terminal or command prompt window where you executed the
dotnet Sendent.Synchronisation.Service.dllstart command.