Alerting

Alerting in IntegraMon ensures that relevant deviations in SAP CPI and edge-related integration scenarios are not only visible but actively reported. This includes functional issues as well as technical and operational problems.

This documentation explains:

• which alert types are available today
• how rules, templates, and notifications work together
• how alerting behaves in productive operations

Structure

• Alert rules, filters, and notifications
• Using alerting in operations
• Alert status and notification reference
• Troubleshooting alerting

Goal of this documentation

This documentation is meant to make the alerting area understandable from an operational point of view while still giving enough technical context to evolve rules in a controlled way later on.

Important upfront note

In day-to-day product usage, the operational CPI alert layer is the relevant one. It works on top of configured jobs, monitored objects, and assigned templates.

Older generic core structures still exist in the code base. They are only covered where they still matter for current behavior.

Typical use cases

• no messages received within an expected time frame
• technical errors or increased error rates in message flows
• certificate or keystore-related issues
• operational notifications driven by email and templates

Need the technical deep dive?

For alert lifecycle, suppress logic, backend processing, worker timing, and data flow details, continue with System Documentation: Alerting.

Need the shared product reference?

For common state meanings, visibility, masking, and role language across the product, see Product Reference.