Non-Events Agent for Nodinite
Stop reacting to problems. Start preventing them.
The Non-Events Monitoring Agent for Nodinite is your early-warning system for integration issues. Instead of waiting for customers to report missing orders, delayed invoices, or failed transactions, you get alerted the moment patterns deviate from normal—often before anyone notices a problem.
Why Non-Events Monitoring is a game-changer:
✅ Catch problems before customers do - Detect missing or delayed messages in real-time, not after complaints
✅ Turn logs into business intelligence - Monitor invoice counts, order volumes, payment confirmations—any business metric from your integrations
✅ Prove SLA compliance automatically - Track response times, message volumes, and processing windows without manual effort
✅ Reduce firefighting, increase proactivity - Shift from reactive troubleshooting to proactive monitoring
✅ Support business charging models - Use message counts and processing metrics for transparent billing
The difference: Traditional monitoring tells you when systems are down. Non-Events monitoring tells you when business patterns are wrong—like receiving only 50 invoices today when you normally receive 500, or a payment confirmation that never arrived after an order was sent.
Real-world impact:
- E-commerce: Alert when order confirmations drop below threshold during peak hours
- Healthcare: Detect missing patient record updates before regulatory issues arise
- Finance: Monitor that every payment request receives an acknowledgment within SLA
- Logistics: Ensure shipping confirmations match booking requests within correlation windows
This diagram visualizes how end-users, administrators, and Log Views enable Non-Events Monitoring in Nodinite.
The Non-Events Monitoring Agent for Nodinite keeps you ahead of issues by alerting you when traffic patterns exceed your defined thresholds.
How it works: Non-Events monitoring analyzes data from Log Views, which display logged events filtered by Search Fields. For this to work, your logged events must have proper Message Types assigned—this determines which Search Field Expressions extract your business data. Without proper Message Types and Search Fields, you won't have the business data needed for effective Non-Events monitoring. Learn more about the Log Event processing pipeline.
- Receive alerts before your customers notice any problems.
- Enhance the experience, quality, and credibility of your integration services.
- Support and maintain integrations according to SLA commitments, and leverage monitoring data for transparent charging models.
This example shows how missing or delayed messages can impact your business. The Non-Events Agent helps you detect and resolve these issues before they escalate.
Features
The Non-Events Agent lets you monitor logged data by re-using Nodinite's security-restricted Log Views for business, IT-ops, and other stakeholders. You can easily perform a search, copy the API link from Log Views, and define the timespan to evaluate. Monitor data from any platform over any selected timespan. Archiving ensures superior long-term logging.
Non-Events (Number-based scenarios)
Use the Non-Events configuration to evaluate straightforward, number-based scenarios:
AckNaks (Request-Response scenarios)
Use the AckNaks configuration to monitor grouped Log Views and request-response scenarios:
Common features
- Fine-tune alerts with thresholds for Errors and Warnings
- Evaluate the actual number of logged events
- Trigger an alert if fewer than the expected number of messages are logged (Min)
- Trigger an alert if more than the expected number of messages are logged (Max)
- Monitor any message type from any endpoint
- Use advanced date/time filtering
- Exclude vacation or non-business dates
- Apply content-based filtering using the rich features of Nodinite Log Views
- Statistics - Use data insights to fine-tune Interval Scheduling
"Simple" Count-based features
- Define user-specific business hours
- Ensure monthly messages arrive within a defined interval (e.g., between the 10th and 25th, once and only once)
"Complex" request-response features
- Evaluate Ack/Nak
- Correlate on any message type (technical/functional)
- Match using data from payload/context
- Set the timespan according to your configuration
- Stay within agreed SLA levels
- Trigger alerts if boundaries are exceeded
- Set the max expected events in a group for sanity checks (detect duplicates or anomalies)
- Receive relevant alert information
Examples
- Require the number of orders received in the last 30 days to be more than 500 and less than 1500.
- Send an alert if the response (ACK/NAK) has not been logged in the given time interval.
- Require the number of accepted orders from customer A on Mondays from 8:03 to 13:37 to be less than 500.
- Require the number of accepted orders from customer A on Mondays between 8:03 to Wednesdays at 13:37 to be less than 500.
- Send a warning alert if the number of orders and invoices to customer A and B is too low, excluding dates: 17/5, 6/6, 4/7, and 24/12.
- Send an exception alert if a response (Ack/Nak) has not been received in the given time interval.
- Alert if large messages over 1337 MB are transmitted.
- Alert if any order has more than 1000 order rows.
- Alert if the total order sum from the selected set of order rows in the order(s) message is more than X.
Actions
- View all delayed Ack/Naks
- View all missing Ack/Naks
- View current status
- Full Interval
- Partial Interval
- Quickly Edit Remote Settings per Resource
Pricing
The Non-Events Agent and all other Monitoring Agents come included in the Nodinite license. You pay no additional costs for using the Non-Events Monitoring Agent if you are a Nodinite licensee.
Release Log
Find detailed information about features and bug fixes in the Release Notes
Next Step
Install Non-Events Monitoring Agent
Configuration of the agent