Data Collector shows Operating Status Failed on Active Experience Monitoring page
search cancel

Data Collector shows Operating Status Failed on Active Experience Monitoring page

book

Article ID: 447718

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

A Data Collector on the Active Experience Monitoring page of the DX NetOps Portal web UI shows a failed state. The "Enabled Status" shows Green and Enabled. The "Operating Status" shows Red and Failed.

The Data Collector (DC) logs show a repeated java.lang.IllegalArgumentException: unsupported URI error every minute. In the NetOps Portal UI, the Active Experience Monitoring page shows the Data Collector as "Enabled" (Green) but the Operating Status as "Failed" (Red).

Symptoms:

  • The netops-data-collector.log contains: java.lang.IllegalArgumentException: unsupported URI https:/api/v3/appliance/#### (Note the missing second slash in the protocol).
  • The Portal PCService.log shows: InvalidArgumentException: Failed to find a value for key 'ProxyUserName'.
  • Attempts to save the Data Collector configuration fail or do not resolve the status when the proxy fields are left blank.

Environment

  • AppNeta Cloud Monitoring integration
  • Environment proxy that does not require authentication

Cause

The NetOps Portal UI requires values for Proxy User Name and Proxy Password when a proxy host/port is specified. If the environment's proxy server is unauthenticated and these fields are left empty, the configuration does not substitute correctly, leading to a malformed API URI.

Resolution

Use dummy credentials to bypass the UI validation requirement.

  1. Log in to the NetOps Portal.
  2. Navigate to the Active Experience Monitoring page. (Administration -> Monitored Items Management -> Active Experience Monitoring)
  3. Select the affected Data Collector and click Edit.
  4. In the Proxy Configuration section, ensure the Proxy Host and Port are correct.
  5. If the environments proxy does not require a username and password, enter dummy values in the Proxy User Name and Proxy Password fields (e.g., use admin for both fields).
  6. Click Save.
  7. Verify that the Operating Status changes to Up (Green) and that the log errors no longer appear.

Note: If the issue persists, ensure that AppNeta SaaS endpoints are whitelisted on the proxy. For defects and enhancements, subscribe to Broadcom Support Article 275360 for updates on fix status.

Additional Information

To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.