Nodinite Serilog sink using a Service Bus queue
Use the Nodinite Serilog ServiceBus with your full framework and .NET Core applications to enable end-to-end tracking. Typical examples include Microsoft Azure functions built with .NET (usually CSharp). Nodinite supports payload Logging and removes the obstacle that Application Insights logging imposes on message size.
Important
Set OriginalMessageType for searchable business data - The Service Bus sink sends your log events to Azure Service Bus queues for reliable asynchronous processing by the Pickup Service. Without proper Message Types, your logged events won't have business data extraction via Search Field Expressions, preventing features like Non-Events Monitoring, Business Process Modeling (BPM), and business-data searches in Log Views from functioning. Always include
OriginalMessageTypein your logging code before deploying to production. Service Bus provides reliable messaging with dead-letter queue support.
Logging Options
Choose one of the following articles based on the solution you want to enable Logging for:
❔'How To Start Logging With Microsoft.Extensions.Logging.ILogger in Azure Functions'
❔'How To Start Logging With Serilog'
Connection Options
Regardless of your choice, include one of the following configurations in your appsettings.json file:
- Service Bus (Using the default Managed Identity)
- Service Bus (Using an explicit Managed Identity)
- Service Bus (Using a Connection string)
Next Step
❔'How To Start Logging With Microsoft.Extensions.Logging.ILogger in Azure Functions'
❔'How To Start Logging With Serilog'
Related Topics
Message Types - Critical for Search Field extraction from Service Bus sink events
Search Field Expressions - Extract business data from logged messages
Log Views - Search logged data by business identifiers
Non-Events Monitoring - Track message volumes and detect missing messages
Business Process Modeling (BPM) - End-to-end transaction tracking
Pickup Service - Processes Service Bus messages reliably