Preferred Data Sources

EntitiesClosed Things deployed in the customer environment that are needed to run the business, such as applications, devices, interfaces, and locations. and objects that are streamed to Riverbed IQ Ops can originate from more than one data sourceClosed 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.. For example, the User Response Time metricClosed A measurement or data point that is monitored and analyzed to detect anomalies and generate incidents. can be sent to IQ Ops from AppResponse and NetProfiler for the same entity. The computations of some of these metrics (generally, applicationClosed An entity type representing software applications deployed in the customer environment that are monitored for performance and anomalies. locationClosed An entity type representing physical or logical locations in the customer environment where entities are deployed and monitored. metrics and, particularly, User Response Time) vary between data source types (AppResponse and NetProfiler), which can complicate incidentClosed 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. behavior and management in IQ Ops.

Rather than merging conflicting data, Riverbed IQ Ops uses a Preferred Data Source setting to select which system defines the Application-Location space. This selection ensures consistent handling of key metrics by streaming data from only one source at a time.

Note: AppResponse is the default preferred data source, and you can change theEdge's configuration to make NetProfiler the preferred data source.
Alert: Changing the preferred data source will reset baselines used for anomalyClosed An unexpected event or measurement that does not match the expected model. detectionClosed One or more indicators that are correlated and may act as a trigger for incident creation or runbook execution. and it will require several days for the system to train against the data ingested from the new preferred data source. Also, there could be performance implications with a large AppResponse deployment.

Important Considerations

The Preferred Data Source setting applies only to Entity type Application-Location metrics that can be sourced either from AppResponse or NetProfiler (e.g., User Response Time and %Total Retrans metrics). This setting does not apply to metrics that are streamed for other Entity types from Netprofiler (e.g., Inbound/Outbound Network Utilization), these non-Application-Location metricswill be streamed regardless of the Data Source Preference.

Note these considerations pertaining to preferred data sources:

Changing the Preferred Data Source

You can change the preferred data source on the Data Sources page.

When you open an Edge to see its data sources, the Data Ingestion column will indicate the Preferred Data Source. If you wish to change this, click the Change button to open the Change Preferred Data Source dialog, which enables you to specify whether to prefer AppResponse or NetProfiler. This is accompanied by a warning about the effects of changing the data source.

Consider talking with Riverbed Support prior to changing the preferred data source.