We’ve configured event monitoring for temperature sensor data in our SAP IoT deployment, but alerts are not firing when thresholds are breached. The alert rules are set to trigger notifications when temperature exceeds 85°C, but we’re seeing values hitting 92°C without any alerts being generated.
I’ve verified the alert rule configuration shows the correct threshold values and the notification channel is configured to send emails to our operations team. The event-processing pipeline shows events flowing through successfully, but the alert engine seems to be bypassing the threshold checks entirely.
This is causing us to miss critical incidents where equipment could be damaged. Has anyone experienced similar issues with alert rule configuration or notification channel setup in SAP IoT? Could this be related to event-processing permissions or role assignments?
Thanks for the suggestion. I verified that the alert rules are enabled - the status shows ‘Active’ in the monitoring dashboard. I also checked the event-processing logs and can see temperature events being received with values above threshold, but there’s no corresponding alert evaluation entry in the logs. It’s like the alert engine isn’t picking up these events at all.
Have you checked the time window configuration in your alert rules? Sometimes alerts won’t trigger if the evaluation window doesn’t align with your event ingestion pattern. For example, if your rule evaluates every 5 minutes but your temperature events arrive every 10 minutes, you might miss threshold breaches between evaluation cycles.
After reviewing your issue, I believe you’re experiencing a combination of configuration problems across alert rules, notification channels, and permissions. Let me walk you through a systematic resolution.
Alert Rule Configuration:
First, verify your alert rule’s event filter syntax. In SAP IoT, the filter must exactly match the event schema being published. Navigate to your alert rule and confirm the event type path matches your temperature sensor’s output format. Common mistakes include case sensitivity issues or incorrect JSON path expressions in the filter condition.
Notification Channel Setup:
Your notification channel needs proper authentication and endpoint configuration. Go to the notification settings and test the channel independently using the ‘Send Test Notification’ feature. If this fails, check:
- SMTP server settings if using email (host, port, TLS settings)
- Webhook endpoint availability if using HTTP notifications
- Authentication credentials validity
I recommend enabling detailed logging for the notification service to capture delivery attempts and failures.
Event-Processing Permissions:
This is likely your main issue. The alert evaluation service requires specific permissions to function:
- Verify the service principal has the ‘IoTEventReader’ role to access the event stream
- Confirm it has ‘AlertEvaluator’ role to process alert rules
- Check that ‘NotificationPublisher’ role is assigned for sending alerts
You can validate permissions by reviewing the service’s role assignments in the SAP IoT administration console under Security > Service Principals. Look for your alert-processing service and ensure all three roles are present.
Additional Troubleshooting:
Enable debug logging for the alert engine by setting the log level to ‘DEBUG’ in the monitoring service configuration. This will show you exactly which events are being evaluated and why alerts might not be triggering. Look for entries like ‘Alert rule evaluation skipped’ or ‘Permission denied’ which will pinpoint the root cause.
After making these changes, restart the alert-processing service to ensure all configuration updates are loaded. Test with a controlled threshold breach to verify alerts are now firing correctly.