Nodinite Serilog sink using Nodinite Log API

Use the Nodinite Serilog sink for the Nodinite Log API 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 Log API sink sends your log events synchronously to the Nodinite Log API for immediate processing. 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 OriginalMessageType in your logging code before deploying to production. Log API sink provides synchronous logging with immediate confirmation but requires direct network connectivity to Nodinite.

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 the following configuration in your appsettings.json file:

• Log API

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 Log API 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

• Serilog - Blob Storage
• Serilog - Event Hub
• Serilog - File
• Serilog - Service Bus