Data Sources Page

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. supply the telemetry that powers analytics, incidents 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., runbooks 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., and the Riverbed Technology data store. Until you add and enable at least one data source, the platform has no data to analyze. The Data Sources page is where you add, configure, and manage those connections. Use it when you onboard a new NPM (Network Performance Monitoring) product, enable a SaaS (software as a service) data source such as NPM+ or Aternity, or need to change which sources are enabled or preferred.

How to open the page

Navigate to the Data Sources Page:

1. Click the Launchpad button ⁝⁝⁝.
2. Click AI Ops > Management.
3. In the Management page, click the Hamburger Icon, then click Edge & Data Sources.

The page opens with tabs for each type of connection. Which tabs you see depends on your tenant and feature flags: Edges (on-premises NPM data sources), NPM+, ATERNITY SaaS, and optionally CloudIM.

Edges tab

The Edges tab is the default. It lists your Riverbed Edge instances and the NPM data sources (for example Riverbed NetIM, Riverbed NetProfiler, Riverbed AppResponse) connected to each.

Use Add an Edge to run the wizard that creates a new gateway (AWS, Azure, or ESXi). Each row shows the edge name, type, status, and a list of data sources with name, type, hostname or IP, info (status and versions), data ingestion (last received and preferred source), and enabled state.

The row menu (...) offers Edit, Connect a Data Source, Obtain VM Image, Download Cloud-Init / Download ISO, and Delete.

Each data source has its own menu: Edit (change IP, type, protocol, enabled) and Delete.

For full setup steps, see Configuring Riverbed Edge and Data Sources and Add an Riverbed Edge wizard. To add a data source to an existing edge, see Adding a Data Source.

NPM+ tab

The NPM+ tab shows your NPM+ SaaS connection. It displays Account ID and Account Environment, an Enable Data Source toggle (to federate NPM+ data into the Riverbed Technology data store), and connection status.

Turn the toggle on to allow Workspaces, Automations, and APIs to use NPM+ data. For setup and configuration, see Enable the NPM+ Data Source.

ATERNITY SaaS tab

The ATERNITY SaaS tab shows your Aternity SaaS connection. It displays account details: Aternity Domain, Account Name, Account ID, and Connector Name (from the Aternity integration and its OData connector).

Enable Data Source turns federation of Aternity data into the data store on or off. Enable Data Ingest turns processing of that data through the IQ Ops analytics pipeline on or off. The page also shows connection status and Last Data Ingested.

You must install the Aternity integration and configure an OData connector from the Integrations Library before you can enable the data source. For setup and configuration, see Enable and Configure the Aternity Data Source.

CloudIM tab

When your tenant has CloudIM enabled, a CloudIM tab appears. Use it to configure cloud data sources for CloudIM.

For details, see Configuring Riverbed Edge and Data Sources (CloudIM section or tab).

Metrics streamed by data source

NPM (Network Performance Monitoring) 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. stream a preconfigured subset of high-value metrics A measurement or data point that is monitored and analyzed to detect anomalies and generate incidents. (key measurements) into the IQ Ops analytics pipeline. These metrics are leading indicators of critical issues and drive incidents 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. and runbook execution. The following table summarizes which key measurements can be streamed from each data source type by entity Things deployed in the customer environment that are needed to run the business, such as applications, devices, interfaces, and locations..

Notes:

1 – User Response Time: Riverbed NetProfiler uses an approximation that does not include connection setup time; Riverbed AppResponse includes it. User Response Time is only processed for named applications (e.g. excludes ICMP, SNMP, TCP_Unknown, UDP_Unknown). For definitions, see metric definitions.

2 – Throughput: Monitored only for VoIP-related applications (VOIP, SIP, RTP).

3 – Client Location: Aternity City/Country/State.

What you can customize

Some data is preconfigured and some can be customized. Key measurements (the metrics streamed into the analytics pipeline) are preconfigured and cannot be changed. What runbooks can query is customizable:

• NPM data in runbooks: Runbook Data Query A runbook node category that gets data about the trigger and forwards it to other nodes in the runbook for further processing. nodes Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. let you choose which metrics, entities Things deployed in the customer environment that are needed to run the business, such as applications, devices, interfaces, and locations., and time ranges to query from connected NPM data sources. You configure this per node in the Runbook Editor. For filters and limits, see Data query properties - Filters and Limits.

• Third-party data: HTTP Request nodes Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. and integration subflows A reusable automation chunk that performs frequently used functions, such as opening a ticket in an external system, and can be used to implement integrations with third-party systems. let runbooks call external APIs and pull in third-party data. Configure the desired API calls in the runbook or install and configure an integration from the Integrations Library. See Webhooks and Integrations Library Page.

Related information

Configuring Riverbed Edge and Data Sources covers gateway and data source setup end to end. Adding a Data Source describes how to connect a data source to an existing edge. Preferred data source explains how to choose a preferred source when both Riverbed AppResponse and Riverbed NetProfiler feed the same scope.