Skip to content

Quickstart

This page is a fast roadmap to go from zero to the thing that matters most: getting a critical alert on your phone. About 15 minutes, assuming your tenant already has hosts connected and some active alerts.

If you have not signed in yet, start with First access. If you want to understand the vocabulary (tenant, hub, agent, alert), read Concepts first.

1. Look at the Cockpit

Right after sign-in the landing screen is the Cockpit. It gives the whole-tenant view on a single page:

  • General Health Score at the top.
  • KPIs (monitored hosts, collection points, configured alerts, APM services).
  • Recent alerts with severity.
  • Top hosts with the most open alerts.

Use the cockpit to calibrate your day: if criticals went up, there is on-call work. If everything is green, time for planning.

Filter by window

The selector on the top right changes the cockpit window (last hour, today, 7 days). The default is 24 hours.

2. Open the Alerts screen

From the side menu, go to Observe & Explore → Alerts. The screen lists every alert that is currently open in the tenant.

The most useful filters to start:

  • Severity: tick only Critical and High to cut the noise.
  • Tag or Host: filter by application (app:checkout) or host family (db-prod-*).
  • Free text: alert name.

Click a row to see the detail: host, metric that fired, state history and notes added by the team. To see alerts that already closed, open Alerts History.

3. Create your first notification rule

Seeing alerts on the portal is useful, but what makes operation happen is the notification on the right channel. Let's wire push to your phone.

First, create the Push channel:

  1. Open Notifications → Channels → New Channel.
  2. Type: Push Notification.
  3. Name: something descriptive, e.g. Personal NOC push.
  4. Save.

The channel uses the mobile app tokens linked to your account (step 4). If you have not installed the app yet, the channel is created but no device is tied to it, and nothing arrives until you install.

Then, create the rule:

  1. Open Notifications → Rules → New Rule.
  2. Severities: tick Critical (you can add High later).
  3. Tags or Hostnames: filter the scope. To skip filtering, leave it empty and the rule picks up every critical alert in the tenant.
  4. Destination channels: select the Push channel you just created.
  5. Cooldown: suggested 10 minutes to avoid being bombarded by repeats.
  6. Save.

From save onward, any new alert matching the rule fires push on your phone. See Channels and Rules to explore other types (Email, Slack, Teams, Webhook, Telegram).

The rule created in step 3 only fires push if a device is tied to your account. For that:

  1. Get the app: App Store (iOS) or Google Play (Android).
  2. Sign in with the same email and password as the portal.
  3. Accept the notification permission the OS asks for on first launch.

The device token is registered automatically on your account. You can install on more than one device (personal phone + corporate) and they all receive. For details, see Mobile app.

Test with a low-severity alert

To confirm the notification works before a real situation, temporarily edit the rule from step 3 to also include Information severity. Wait for the next informational alert to come in, confirm the push showed up, then revert the rule back to Critical only.

5. Next steps

You have the basic loop running: alerts on the portal and push on the phone. From here the path depends on your role.

  • Build your dashboards

    Compose custom views for your team (NOC, infra, database, application).

    My Dashboards

  • Explore Infrastructure

    Navigate hosts, containers, storage and network of the tenant.

    Hosts

  • APM and applications

    Track latency, throughput and errors of your applications with full observability.

    APM

  • Administer the tenant

    Register hosts, manage agents and collectors, plan maintenance windows.

    Agents & Hubs