- 7 minutes to read

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
graph LR roUser(fal:fa-users-class End-user) roLV(fal:fa-hard-drive Log View) roAdmin(fal:fa-user-cog Nodinite Administrator) roNE[fal:fa-alarm-clock Non-Events Monitoring] roUser --> | Search for business transactions | roLV roAdmin --> | Manage/Edit | roLV roLV -...-> | Enables | roNE

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.

Delayed Transactions
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

Most integration problems that hurt the business aren't errors. Nothing fails, so every system shows green. Non-Events catches what didn't happen, or what happened in the wrong amount:

Kind Example How Non-Events catches it
Nothing arrived Friday at 2 PM, orders from the web shop stop coming in. All systems show green, because nothing has failed. Nothing happened, and that is the problem. A Min threshold on the order count during business hours, for example at least 1 order per hour.
⏱️ Too late The payment file reaches the bank after the cut-off time. Suppliers are paid a day late. An interval that ends at the cut-off with Min 1 for the payment file, or an AckNak that expects the bank's receipt within the agreed time.
Too few A retail chain normally sends about 400 orders an hour on a weekday. Today it has sent 40. A Min threshold per interval, with a Warning level well above the Error level. Exclude holidays and weekends with date exclusions.
Too many 50,000 messages where 500 is normal. A loop is sending the same invoices again. A Max threshold per interval, so a runaway sender raises an alert within the interval.
Too big A 100 MB message where 200 KB is normal. Someone sent the whole register instead of today's changes, and it blocks the queue. A Log View that shows only messages above the size you expect, monitored with Max 0.
Sanity check Today's exchange rates weren't loaded by 08:00, so the invoices go out with yesterday's rates. An interval on weekdays that ends at 08:00, with Min 1 for the exchange-rate message.
Wrong content An order with quantity zero, or an invoice without a due date. Technically valid, wrong for the business. Search Fields that extract the quantity and the due date, a Log View filtered on the wrong values, and Max 0.

The same building blocks combine freely: count orders from one customer on Mondays between 08:03 and 13:37, compare a 30-day total against a range, or alert when an order has more than 1,000 order rows.

Actions

  • View all delayed Ack/Naks
  • View all missing Ack/Naks
  • View current status
    • Full Interval
    • Partial Interval
  • Quickly Edit Remote Settings per Resource

Common Questions

How do Non-Events and AckNak differ? When do I use each? Non-Events monitors volume/counts (e.g., "alert if orders <500/hour"), AckNak monitors request-response correlation (e.g., "alert if payment request has no acknowledgment within 30 seconds"). See Non-Events and AckNaks.

Can I monitor data from multiple systems/platforms? Yes—any system logging to Nodinite can be monitored, including cloud, on-premise, and partner systems. See Features.

How do I handle seasonal/variable business patterns? Use date exclusions (holidays, weekends) and multiple threshold configurations for different time periods. See Common features and the Examples.

Can Non-Events monitor data quality issues not just volume? Yes—monitor any Search Field values or payload content (e.g., "alert if messages >1MB" or "alert if order totals >$100K"). See the Examples.

How do I configure AckNak correlation when Request/Response use different fields? Use Search Field Expressions to normalize correlation keys across different message formats. Learn more

View all FAQs → Complete FAQ Index

Pricing

The Nodinite 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 Steps

Install Non-Events Monitoring Agent
Configuration of the agent
Troubleshooting Overview - View all FAQs

Prerequisites for Non-Events Agent
Monitor Views
Monitoring Agents Troubleshooting – Install, diagnostics, and multiple instances for any Monitoring Agent