Troubleshooting Missing Data in Dashboards

Overview

When data does not appear in Cisco Crosswork Assurance dashboards, the issue often relates to connector configuration or data pipeline problems. Use this guide to systematically diagnose and resolve the issue.

Quick Diagnostic Checklist

• Verify Sensor Collector is receiving data
• Check connector configuration version
• Confirm data pipeline connectivity
• Review data ingestion status
• Validate metric mappings

Common Cause: Outdated Connector Configuration

When using Sensor Agent or Telemetry Collector with an older Sensor Collector version, data may not forward properly.

Check Connector Configuration Version

Use the API to verify the metricMappingsVersion field:

GET {{tenant-server}}/api/v2/connector-configs/{{connectorId}}

Note: The connectorId can be found in the Analytics UI URL when the connector is selected.

CAUTION: The version displayed in the Analytics UI is the template version, not the stored configuration version.

Solutions

Option 1: Delete and Recreate the Connector (Recommended)

This is the simplest and fastest solution.

CAUTION: Downloading a new Sensor Collector alone is NOT sufficient. The connector configuration will not be updated. The connector MUST be deleted.

Option 2: Update the Connector Mapping Configuration

Use this if the connector has customized elements:

# Get current configuration
GET {{tenant-server}}/api/v2/connector-configs/{{connectorId}}

# Modify the configuration as needed

# Update the configuration
PUT {{tenant-server}}/api/v2/connector-configs/{{connectorId}}

Verifying Sensor Collector Configuration

Check Sensor Collector Logs

When Sensor Collector starts, verify it received configuration and is listening on the correct ports:

sudo docker logs <roadrunner_container_id>

Expected Output:

14:17:49.921 connect Γû╢ INFO Successfully connected to DataHub
14:17:49.921 getConfig Γû╢ INFO Requesting config from DH
14:18:52.101 processMetaMsg Γû╢ INFO Received config from DH
14:17:52.951 func1 Γû╢ INFO server OpenMetricsPushGateway listening on 0.0.0.0:55888 with TLS enabled
14:17:52.952 func1 Γû╢ INFO server AgentProxy listening on 0.0.0.0:55777 with TLS enabled

WARNING: If logs only show "Requesting config" without "Received config", Sensor Collector is not receiving its configuration.

Check Exposed Ports

docker ps

Verify ports are exposed for both IPv4 and IPv6:

• 0.0.0.0:55777->55777/tcp (IPv4 management)
• :::55777->55777/tcp (IPv6 management)
• 0.0.0.0:55888->55888/tcp (IPv4 data)
• :::55888->55888/tcp (IPv6 data)

Data Pipeline Verification

Check Data Flow

1. Sensor Agent sends data to Sensor Collector (port 55888)
2. Sensor Collector forwards to Crosswork Assurance backend (port 443)
3. Crosswork Assurance processes and stores data

Verify Each Stage

# Check agent is sending data
docker logs <agent_container_id> | grep -i "sending"

# Check Sensor Collector is forwarding
docker logs <roadrunner_container_id> | grep -i "transmit"