Skip to main content

TagoDeploy Monitoring

The TagoDeploy Monitoring app watches the infrastructure your TagoDeploy project runs on and lets you react when a resource crosses a limit you set, by notification or by automation.

It works one level below your TagoIO application. It does not watch your dashboards, devices, or data. It watches the services and resources underneath them, such as databases, middlewares, MQTT brokers, and your account spend.

Why use it​

Infrastructure problems are quiet until they reach your users. A database running hot, or a month's spend climbing past budget, is something you want to know about early, before it becomes a slow dashboard or an unexpected bill. Monitoring catches those conditions at the resource level and lets you act on them, by alerting someone or by running an automated response.

What you can monitor​

Each rule reads one metric from one resource. Resources come from the project's services:

  • TagoIO Platform services, such as the Main Database.
  • Installed middlewares.
  • MQTT brokers.
  • Account billing, to track month-to-date spend against a budget you set.

The available metrics depend on the resource, for example CPU utilization for a service, or the budget for billing.

How it works​

Monitoring connects alerts, actions, and logs:

  • Alerts are the rules. Each watches a resource metric and defines the thresholds that should trigger.
  • Actions are the response: an email, an SMS, or a webhook to any endpoint.
  • Logs are the record of every check and trigger, for confirmation and troubleshooting.

The monitor checks each enabled rule regularly. When a metric crosses a threshold, it runs that threshold's actions and writes the result to the log. A cooldown on the rule keeps a sustained condition from notifying you over and over.

Typical setup​

  • Create an action for how you want to be notified, or what you want to run.
  • Create an alert: pick the resource and metric, set the thresholds, and point them at your action.
  • Watch the Logs to confirm checks run and alerts fire as expected.