An event is a point in time that represents the state of a service, application or infrastructure component. The state can be from a specific component of a service, application or infrastructure. Monitoring tools can generate events when potential problems are detected in your infrastructure.

Events can be ingested as two unique types:

Monitoring Events

  • Monitoring Events
  • Webhook Calls
  • Emails
  • SNMP Traps

Change Events

  • Service Changes
  • Deploys
  • Builds

Each time information around a state is produced, it counts as an event. It doesn’t have to be a problem - in fact, most are normal and do not require action.

Over time status updates and repeat events may occur from the same system issue. In BigPanda, raw event data is merged into a singular alert so that you can visualize the life cycle of a detected issue over time.

When an alert is resolved and then reopened during an incident it belongs to the same entity as the original alert and will appear on the same line within the Incident Timeline view. This makes it easy for you to spot reoccurring alerts.

For example, a CPU load alert may start with a warning event, then increase in severity with a critical event, and finally get resolved with a resolution event. All three of these events will be merged into a single alert. Common events that are sent to BigPanda include: “CPU > 95% for more than 5 minutes” and “Port X on Router ABC down”

BigPanda correlates related alerts into incidents for visibility into high-level, actionable incidents.


Incident, Alert, and Event

1 - Incident
2 - Alert
3 - Event



Some monitoring tools refer to events as ‘alarms’ or ‘alerts.’ In BigPanda documentation ‘alert’ is always used to refer to the complete lifecycle of an event.