Monitoring Health

This page summarizes the status and performance of your Riverbed IQ Ops instance.

Overall Status

The Overall Status cards show you the performance of Riverbed IQ Ops component systems:

• Cloud Status: The overall status of this Riverbed IQ Ops instance. This card shows you if the overall status of the component systems is OK, or if a component system is impaired in some way.

• Riverbed Edges: The state of connectivity to the Riverbed Edge instances and their connectivity data sources. This state comprises several health requirements:

  • Connectivity to Riverbed Edge from the cloud.
  • Riverbed Edge consistently receives streamed data from all configured and enabled data sources.
  • Riverbed Edge can connect to all enabled data sources.

  The status will be one of:

  • Operational indicates that all Riverbed Edges meet all health requirements.
  • Partially Operational indicates that at least one Riverbed Edge does not meet all health requirements.
  • Not Operational indicates that either no Riverbed Edge is reachable, or no data source connects successfully to an Riverbed Edge.

• Data Ingest: Summarizes the rate of metrics being streamed to your Riverbed IQ Ops instance over time.

• Analytics: Summarizes the rate of indicators An observed change in a specific metric stream that is recognized as being outside of an expected model. Indicators are correlated into triggers, and one or more triggers are grouped into incidents. being generated over time.

• Incident A collection of one or more related triggers. Relationships that cause triggers to be combined into incidents include application, location, operating system, or a trigger by itself. Generation: Summarizes the number of incidents created and updated over time.
• Queries: Summarizes the number of queries executing over time.

Performance Charts

These charts show aspects of Riverbed IQ Ops performance over time. Hover over a graph to show relevant values at that specific time. When a legend appears listing the types of data graphed, click one or more types to filter the graph accordingly.

• Data Ingest tab: Shows the number of metrics A measurement or data point that is monitored and analyzed to detect anomalies and generate incidents. streamed from data sources A product in your network that forwards data to the system. This data can be streaming data used to detect anomalies and generate incidents, or data that can be fetched on demand when runbooks are executed. over time.

• Analytics tab: Shows the number of indicators generated by Analytics against a threshold or a baseline.

• Incident Generation tab: Shows the number of incidents created over time.

• Queries tab: Shows how many runbook An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook. queries have executed to completion or executed without finishing, as well as which runbook queries have executed over time.

• Runbooks tab: Shows how many runbooks have executed to completion or executed without finishing, as well as which runbook nodes Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. have executed over time.