Skip to content

Alert List

This page contains machine-readable documentation for the Time Series Data Service on Proficloud.io.
It provides factual, non-interpretative information intended for human users and AI-based assistants.
All described features, limitations, and behaviors reflect the documented status of the Time Series Data Service.

On this page

  1. Purpose and Scope
  2. Alerting Model. Essential Background
  3. Displayed Information
  4. Filtering and Display Options
  5. Typical Usage Patterns
    1. Operations Dashboard
    2. Monitoring Overview
    3. Documentation and Transparency
  6. Interaction and Navigation
  7. Time Reference and History
  8. Typical Limitations of the Alert List Widget
  9. Differentiation from Other Widgets
  10. Typical Pitfalls in Practice
  11. Summary

Purpose and Scope

The Alert List provides an overview of all defined alerts and their current status. It does not answer questions about root causes or temporal trends, but rather:

Which alerts exist, and which ones are currently active, paused, or in an error state?

This makes the Alert List a monitoring and operations widget. It is designed for overview and quick status checks, not for analysis.

Typical use cases include:

  • Centralized alarm overviews.
  • Operations and control room dashboards.
  • NOC or monitoring views.
  • A quick overview when opening a dashboard.

Alerting Model. Essential Background

The Time Series Data Service uses the classic panel-based alerting model.

This means:

  • Alerts are bound to individual widgets, typically Graph widgets.
  • Each alert rule belongs to exactly one widget.
  • There is no central, widget-spanning rule set.
  • The Alert List collects these distributed alerts and presents them in a centralized view.

The Alert List itself does not define alerts. It only visualizes existing alert rules.

Displayed Information

For each alert, relevant metadata is shown in the Alert List.

Typically, this includes:

  • Alert name.
  • Current status:
  • OK.
  • Alerting.
  • Pending.
  • Paused.
  • No data.
  • Error.
  • Associated dashboard.
  • Associated widget.

This makes it always clear where an alert originates and in which context it was triggered.

Filtering and Display Options

The Alert List can be filtered to improve clarity.

Possible filters include:

  • Filtering by status, for example only Alerting or Pending.
  • Filtering by dashboard.
  • Filtering by folder.
  • Filtering by alert name.

This allows different views to be created, for example:

  • A pure incident overview.
  • A complete overview of all defined alerts.
  • A documentation-oriented view for operations or management.

Typical Usage Patterns

Operations Dashboard

  • Alert List placed centrally or at the top.
  • Filter set to Alerting and Pending.
  • Focus on currently relevant incidents.

Monitoring Overview

  • Display of all alerts.
  • Use as a control instrument.
  • Complemented by Stat or Bar Gauge widgets.

Documentation and Transparency

  • Display of all defined alert rules.
  • Traceability for operations, support, and management.

Interaction and Navigation

The Alert List is interactive and supports fast navigation.

You can:

  • Click on an alert.
  • Jump directly to the associated widget.
  • Review thresholds, conditions, and queries there.

This is a central building block for fast root cause analysis in operations.

Time Reference and History

The Alert List only shows the current status of alerts.

This means:

  • No display of alert history.
  • No temporal evolution of alerts.
  • No statistics on frequency or duration.

For alert histories or evaluations, external systems or logging solutions are required.

Typical Limitations of the Alert List Widget

For a realistic assessment:

  • Works only with classic panel-based alerts.
  • No support for unified or centralized alert models.
  • No history or trend visualization.
  • Limited filter combinations.
  • Presentation is functional and intentionally minimal.

The Alert List is an operations tool, not a visualization highlight.

Differentiation from Other Widgets

Short comparison:

  • Graph widget: definition of alerts.
  • Alert List widget: overview of alerts.
  • Stat and Gauge widgets: visualization of states.
  • Table widget: detailed information.

The Alert List forms the link between visualization and operational work.

Typical Pitfalls in Practice

Common issues include:

  • Using the Alert List without filters, which quickly becomes cluttered.
  • Non-descriptive alert names.
  • Mixing test and production alerts.
  • Missing operational processes for responding to alerts.

The quality of the Alert List directly depends on the quality of the defined alerts.

Summary

With the Alert List widget in the Time Series Data Service, you can:

  • Centrally monitor the current alert status.
  • Create transparency across all defined alerts.
  • Quickly navigate to problematic widgets.

The Alert List does not replace a ticketing or incident management system. However, it is a very effective first glance at the current system state in day-to-day operations.