Adding AppNeta Paths to a Service View ODC-Ingested

Products

• DX OI SaaS
• DX Operational Observability
• DX Operational Intelligence
• DX SaaS
• DX APM SaaS

Issue/Introduction

AppNeta metrics, alarms, and inventory are ingested into DX Operational Intelligence through the Operational Data Connector (ODC). Customers expect the ingested AppNeta Web and Network paths to appear automatically within a specific Service view, but the paths are not assigned to any service after ingestion. This article explains why and how to add them.

Environment

DX Operational Intelligence SaaS
Operational Data Connector (ODC) integration with AppNeta
Service Analytics (Service views)

Cause

ODC does not natively manage Service view membership. The connector ingests AppNeta metrics, alarms, inventory (CIs), and topology and applies attributes to those entities, but it does not assign entities into a named Service view. Service view membership is defined within Service Analytics, independently of the connector, so ingested paths do not populate a service automatically.

Resolution

Add the AppNeta paths to the Service view manually in Service Analytics:

1. Open the target service and select Edit Service, then Manage Elements.
2. Under "1. Select Source," change the source from Applications to Network Services (or Network, depending on how ODC classified the paths).
3. Under "2. Select Base Attribute for Definition," choose the attribute that identifies the paths. This attribute becomes the membership Filter on each row.
4. Use the search box to locate the AppNeta Web/Network paths, click the "+" next to each one (they collect under Selected Elements), then click Add.
5. For membership that keeps up with new paths, define the base attribute/filter on a shared attribute (for example a site, application, or source tag) so future matching paths are included automatically.

The associated metrics and alarms follow the path CI once it is a member of the service, so they do not need to be added separately.

Additional Information

If the paths do not appear under Network Services, switch the source to Network, as ODC classification can vary. If no consistent attribute exists to key a dynamic filter on, inspect a sample ingested path to determine the available attributes before defining membership.