Nodinite Serilog sink using Blob Storage Container
Use the Nodinite Serilog AzureBlobStorageSink 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 Blob Storage sink writes your log events to Azure Blob Storage for 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. Blob Storage is the recommended sink for large payloads and high-volume scenarios.
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:
- Blob (Using the default Managed Identity)
- Blob (Using an explicit Managed Identity)
- Blob (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 Blob Storage 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 Blob Storage events asynchronously