Skip to content

Monitors

Monitors are the core building blocks of Pulse. Each monitor watches a specific aspect of your OT infrastructure and creates incidents when problems are detected.

Monitor list showing S7 monitors with status indicators

Monitor Types

Pulse supports several types of monitors:

OPC UA Endpoint Monitor

Checks connectivity to an OPC UA server. Verifies that the server is reachable and responding to connection requests.

  • Endpoint URL -- The OPC UA server address (e.g., opc.tcp://192.168.1.100:4840)
  • Security Mode -- None, Sign, or Sign & Encrypt
  • Security Policy -- None, Basic256, Basic256Sha256
  • Authentication -- Anonymous, Username/Password, or Certificate

OPC UA Node Monitor

Monitors a specific data point on an OPC UA server. Supports threshold-based alerting.

  • Node ID -- The OPC UA node to monitor
  • Operation -- Comparison: Equal (=), Not Equal (≠), >, ≥, <, ≤
  • Threshold -- The value to compare against
  • Aggregation -- How to aggregate values: Min, Max, Sum, Average, Count
  • Check Frequency -- How often to check the value
  • Evaluation Duration -- Time window for aggregation

S7 Endpoint Monitor

Checks connectivity to a Siemens S7 PLC.

  • IP Address -- PLC network address
  • Rack -- PLC rack number (typically 0)
  • Slot -- PLC slot number (typically 1 for S7-1200/1500)

S7 Tag Monitor

Monitors a specific data tag on an S7 PLC. Supports the same threshold and aggregation options as OPC UA Node Monitor.

  • S7 Address -- Tag address in S7 format (e.g., DB1.DBW0, DB2.DBD4)
  • Data Type -- How to interpret the PLC memory: Bit, Byte, Word, DWord, Int, DInt, or Real

CVE Monitor

Tracks published Common Vulnerabilities and Exposures (CVEs) that affect a specific device. Pulse queries the security advisory catalog every 6 hours and raises an incident for each newly applicable CVE.

  • Vendor -- Device manufacturer (e.g., Siemens)
  • Order Code -- Device order number / MLFB used to match advisories (e.g., 6ES7518-4AX01-0AB0)
  • Firmware Version -- Optional. Narrows matches to advisories that affect this specific firmware version.

Each applicable CVE becomes a separate incident. When a CVE no longer applies (e.g., after a firmware update), the incident is automatically resolved.

INFO

CVE monitoring requires a license that includes CVE monitoring. If your license does not include this feature, the CVE Monitor create page shows an informational message. Contact your administrator to enable it.

Stale Data Indicator

OPC UA Node monitors and S7 Tag monitors show an amber stale badge when no valid sample has been received since the last successful reading. The badge displays how long the monitor has been without data and shows the exact timestamp of the last good sample as a tooltip.

A monitor is considered stale when the server reports that the most recent value is unreliable (for example, because the underlying PLC connection dropped or the tag is not available). Staleness is resolved automatically when a new valid sample arrives.

Filtering Monitors

The monitor list supports several filter options:

  • Status -- Filter by Healthy, Unhealthy, or Unknown
  • Type -- Filter by monitor type (OPC UA Endpoint, OPC UA Node, S7 Endpoint, S7 Tag, CVE)
  • Tags -- Filter by custom tags assigned to monitors
  • Stale data -- Show only monitors whose last sample is stale (OPC UA Node and S7 Tag monitors only)
  • Muted only -- Show only monitors that are currently muted
  • Search -- Text search across monitor names

Quick filter buttons at the top of the list let you filter to OPC UA, S7, or CVE monitors in one click.

Monitor Details

Click on any monitor to view its detail page.

Monitor detail page showing configuration and activity feed

The detail page shows:

  • Status -- Current health status (Healthy or Unhealthy) with last check timestamp
  • Configuration -- Monitor-specific settings (e.g., IP Address, Rack, Slot for S7 Endpoint)
  • Activity Feed -- Chronological history of status changes and events
  • Tags -- Tags assigned to the monitor for categorization
  • Actions -- Edit, mute, or delete the monitor via the Actions button

Importing Monitors from CSV

Organization administrators can create monitors in bulk from a CSV file. See Importing Monitors from CSV for the full walkthrough and the complete column reference.

Muting Monitors

You can temporarily mute a monitor to suppress incident creation during planned maintenance. Muted monitors continue to check their targets but will not generate new incidents.

TIP

Muting is useful during planned maintenance windows. Remember to unmute monitors after maintenance is complete.