Sentinet³ Core · Operations

Alerts and automation

Events become timely communications, clearly assigned responsibilities and, where appropriate, corrective actions.

Targeted notifications

The right channel, with the technical context you need

When a metric crosses a threshold or a service changes state, Core triggers notifications and passes on the technical context needed for diagnosis. The channel is chosen according to the type of event and the operational configuration.

Notification channels

  • Email
  • SMS
  • Voice

For environmental scenarios, also

  • SNMP traps
  • HTTP POST
  • Notifications to mobile devices
Status panel of a monitored service showing attempts, check times, enabled notifications and run-time commands
Status information for a service: check results, notifications and run-time commands.
Escalation and on-call

No alert depends on a single operator

Contacts can be organised into groups and hierarchies. If the problem persists beyond the set interval, the system hands responsibility for the alert over to the next level.

  1. The event reaches the relevant on-call group.
  2. The problem persists beyond the set interval.
  3. The alert moves up to the next level of the hierarchy.
Anti-flooding

Fewer messages, same information

Anti-flooding sets a maximum number of notifications per event within a given time window. Events exceeding the limit are queued and sent in aggregated form.

During a widespread outage the information content is preserved without needlessly multiplying messages.

Proactive automation

From alert to corrective action

The platform can invoke preconfigured commands and sequences when specific conditions occur.

  • Restarting a service
  • Running a maintenance script
  • Activating a mitigation device

Carefully designed actions. Actions must be authorised and designed with reversibility, dependencies and service continuity in mind.

Traceability

Records include state changes, notifications, SNMP traps, logins and system logs. The information can be exported in the formats provided by the platform for further processing or reporting needs, for example together with SLA reports.

Scenario

Gradual saturation of a service

A mail service keeps responding, but free disk space is steadily shrinking. Core detects the threshold breaches, notifies the people responsible and can trigger a pre-authorised automated mitigation procedure. The operator reviews history and graphs to assess urgency and prevent an outage.

All scenarios

Related topics

Want to see Sentinet³ on your infrastructure?

Tell us about your environment: sites, technologies, critical services. We will show you how Core and Infinity can work on your case.