Platform capability

Monitoring

Metrics, logs, dashboards and alerts for the platform, every app it runs, its hosts and the network gear between them, in one stack.

MetricsLogsDashboardsAlertsNetwork devices

What you get

Monitored from the moment it is installed

Each package declares the metrics it exposes, and the platform starts collecting them when the package installs. Nothing waits on a separate setup.

Hosts and network gear together

Servers report through the agent. Switches, firewalls and access points are polled over SNMP and send syslog and traps, so a switch and a server share the same dashboards.

One place for logs

Logs from services, applications, hosts and devices land in one searchable store, along with security findings where those integrations run.

Dashboards that arrive with the app

Packages provision their own Grafana dashboards as they install, over both metrics and logs.

Alerts that reach the right people

Alerts are routed by label, grouped into one notification, silenced during planned work, and handed to an on-call service such as PagerDuty or GoAlert.

One stack for platform and apps

The applications the Site runs are monitored on the same terms as the platform itself, so there is no second monitoring tool to maintain.

Where it fits

Monitoring is one of eight capabilities in the ResorsIT Platform. Every one of them shares the same sign-on, the same permissions and the same audit trail.

Explore the whole platform

The details

A small IT team usually finds out about a problem from the person it happened to. Monitoring exists, but it covers whatever someone remembered to set up, the network gear sits in a separate tool or none at all, and the logs that would explain the problem are spread across a dozen machines. ResorsIT treats monitoring as part of the platform rather than an add-on, so coverage grows as the Site does.

Collecting From Everything

Telegraf runs on each monitored host and writes metrics to InfluxDB, the time-series store. When a package installs, it declares the endpoints it wants scraped and the installer adds them to Telegraf’s configuration, so a service is monitored from its first minute. Fluent Bit collects logs from the same services and hosts and writes them to OpenSearch, which gives the Site one searchable place for everything its services and hosts emit.

Network Devices on the Same Footing

Switches, firewalls and access points run their own firmware and cannot host an agent, so they are monitored from the discovery host that already reaches them. Interface and health metrics are polled over SNMP into InfluxDB, each device’s syslog stream goes through Fluent Bit into OpenSearch, and its SNMP traps feed the same alerting path as everything else. A failing switch port and a failing server raise alerts the same way.

Dashboards and Alerts

Grafana sits over both stores, so one dashboard can show a service’s metrics beside its logs, and packages bring their own dashboards when they install. AlertManager decides what becomes of each alert: routing it by label, grouping related alerts into one notification, silencing alerts during known work, and delivering them to chat or a notification service. Karma gives one view of what is firing, with acknowledgement built in. On-call schedules and escalation are left to a dedicated service, PagerDuty commercially or GoAlert in open source, so each Site chooses the one that fits its rota.

For simple uptime checks of websites and services, ResorsIT also offers Uptime Kuma.