Enable Monitoring
Unlock proactive, end-to-end monitoring for your integration landscape. This guide shows you how to leverage Nodinite Monitoring Agents to gain real-time visibility into the Nodinite LDAP Web API, receive actionable alerts, and ensure business continuity.
✅ Get instant alerts for business-critical issues
✅ Monitor every integration point with specialized agents
✅ Prevent missed events and downtime with Non-Events monitoring
✅ Ensure certificate health and compliance
Nodinite empowers you to monitor the status of your systems and receive alerts whenever a potential business problem arises. By using Monitoring Agents, you tailor your monitoring strategy to fit your unique integration needs. Depending on how you use the Nodinite LDAP Web API, one or more of these agents help you achieve true end-to-end monitoring.
With Nodinite, you receive alerts whenever any monitored component reports a bad status. Proactive monitoring and logging form the foundation for Non-Events, so you get notified before you miss expected events. Certificate monitoring is essential—if you use certificates and follow the 'How to perform hardening on your Nodinite LDAP Web API' user guide, remember that certificates age—replace them before they expire to maintain security and compliance.
Understanding What to Monitor
The LDAP Web API is an ASP.NET Core (.NET 10) web application hosted in IIS or Azure App Service. It sits between your integration platform and the LDAP Catalog Service, so a failure anywhere along that path stops directory operations. The diagram shows which Nodinite Monitoring Agent watches each part.
Diagram: the solid arrows show the LDAP Web API's runtime path; the dotted arrows show which Monitoring Agent watches each component.
What Each Agent Covers
| Component | What can go wrong | Monitoring Agent |
|---|---|---|
| IIS site and App Pool | App Pool stopped, site down, server certificate expires, errors in the Windows event log | Windows Server |
| REST endpoint | Endpoint not responding, slow responses, HTTPS certificate expires | Web Services |
| Log files | Errors written by Serilog when you log to files, see Logging | Log File Parser |
| Message volume | Expected LDAP operations don't arrive, based on Logging events | Non-Events |
| Azure App Service hosting | Web jobs, storage queues, files, and blobs used by the solution | Azure Agent |
| LDAPS certificates on the directory | Domain controller certificate expires, see SSL-LDAPS for Active Directory | Windows Server |
Available Monitoring Agents
Depending on the platforms that call the LDAP Web API, add the agents that cover them:
| Monitoring Agent | Description | |
|---|---|---|
| Azure Agent | Web jobs, Azure storage (Queues, Files, Blobs) | |
| Azure Logic Apps | Logic Apps | |
| Boomi | Boomi Integrations | |
| Database | SQL Server, Azure SQL Database, PostgreSQL | |
| Dynamics 365 Monitoring Agent | CRM | |
| File Folder | File (SMB), File (NFS), SFTP, FTP/FTPS | |
| IBM MQ Monitoring Agent | WMQ | |
| IBM DataPower Monitoring Agent | DataPower, Disk, ... | |
| Log File Parser Monitoring Agent | Content and Log Files | |
| Message Queuing Agent | ServiceBus (Queues and Topics), MSMQ, ActiveMQ, AnypointMQ | |
| Microsoft BizTalk Server | BizTalk Artifacts, Health check, Environment | |
| Mule ESB | Mule ESB, MuleSoft, Cloudhub | |
| Non-Events | Non-Events | |
| RabbitMQ Monitoring Agent | RabbitMQ | |
| Web Services | Web Services, SOAP, REST, Certificate Monitoring | |
| Windows Server | Services, Disk, Memory, CPU, Scheduled tasks, IIS, Ping, Event log, Certificates, PowerShell, Network |
Next Steps
- Explore Monitoring Agents to find the best fit for your environment
- Review Non-Events Monitoring Agent to prevent missed business events
- Learn about Hardening LDAP Web API for certificate management best practices