Core Concepts


Events and actions performed by users and resources are constantly being internally dispatched and notified. The generated information can be listened in realtime and saved for further analysis and traceability.


Every event can be identified by common fields:

  • Topic
  • Date and time
  • Hostname
  • Organization (Customer)
  • Operation (e.g. CRUD)
  • Index (event type description)

Data is consistenly organized in different indexes (tasks, monitors, hosts, file and agent).


CRUD Events

Every time a CRUD action is performed (POST, PUT, DELETE) an event is emitted as follow:

The topic matches the API-crud format, where API is the model name. An "operation" key is added to the event data.

For example, you'll find a monitor operation as a monitor-crud topic.

Non-CRUD Events

This is the list of fixed Non-CRUD events implemented so far:

  • agent-version: every time the agent version is updated.
  • host-stats: every time host-status is updated
  • monitor-execution: every time the agent sends an update for a monitor execution
  • monitor-state: every time a monitor status changes (failure, recovery, stop, change-file)
  • triggered-webhook: every time a webhook is played
  • task-execution: every time a task is played
  • task-result: every time a task excution ends