Asynchronous Logging with Nodinite
Unlock reliable, end-to-end logging for your integration solutions using Nodinite's asynchronous message logging pattern. This approach eliminates system dependencies, prevents overload, and ensures your business-critical events are always captured—no matter the platform.
What you'll find on this page:
✅ Agent-based, appender, and custom logging options
✅ Seamless integration with any platform or technology
✅ Robust, vendor-neutral logging strategy
✅ Best practices for reliable, decoupled event delivery
Enable reliable end-to-end messaging using the asynchronous message logging pattern and avoid dependencies and overloading of any of the systems used for your system integration solutions
Some integration platforms and technologies offer built-in tracking or have a way to attach a log appender. This makes it easy to get logged events and data from your application, flow, or solution to Nodinite. Explore the main options below.
Agent based
Nodinite fetches events from the integration broker; more or less this is plug and play!
Log Appenders
Nodinite fetches events using an appender added to the trace configuration. Usually combined with the Nodinite Pickup Service.
- Serilog
- Use it with Azure Functions(!)
- .NET 5-8 solutions
- WCF Diagnostics Tracing – Fetch events including the payload from the IIS trace
- Log4Net Appender
Solution specific
The Nodinite Pickup Service asynchronously fetches Nodinite JSON Log Events from an intermediate storage.
With our partners and customers, we've enabled logging to Nodinite using the following products:
- Azure API Management Service – Policy-based logging
- Apache Camel
- GhostNodes
- Boomi Integration
- WSO2 - Enterprise Integrator
- WSO2 - API Manager
- iCore – Custom Logging
- MoveIt – Custom Logging
- IBM Sterling – Custom Logging
- Software AG (webMethods) – Custom Logging
If you need additional information about Custom Logging, contact our support for further guidance.
Logging with other products
Nodinite logging is suitable for solutions built on other technologies, including point-to-point (P2P) integrations:
- Databases
- SSIS
- FTP/SFTP
- Files
- Scheduled Tasks (e.g., PowerShell scripts)
- Lightweight integration services and direct APIs
No vendor lock-in
Some platforms require you to add custom code to emit events and data.
Tip
Make sure your logging strategy is not vendor-specific. Your logging logic should be easy to enable/disable, and it should be possible to manage log destinations without redesigning solutions already in production.