Asynchronous Logging with Nodinite
Enable reliable end-to-end messaging using 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 at least have a way to attach a log appender. This makes it very easy to get logged events and data from the application/flow/solutions to Nodinite; Some good examples follow 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.
On our own and with our partners and customers we have enabled Logging to Nodinite using the following other 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
The Nodinite Logging is suitable for solutions built on other technologies, like point-to-point (P2P) using any of the listed technologies:
- Databases
- SSIS
- FTP/SFTP
- Files
- Scheduled Tasks with a script written with for example Powershell
- 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 the log destinations without redesigning the solutions already in production.