Collectors - Sensor

Overview

Sensor Collector (formerly Roadrunner) configurations define the data collection parameters based on the required datasource. The datasource can be Cisco Provider Connectivity Assurance Sensors (formerly Accedian sensors) or third-party sources. Once set up, you can download the collector image with the configuration already included and ready to deploy.

For a walkthrough of collector configuration and deployment, see:

• Deploying Sensor Collector in Docker
• Deploying Sensor Collector in Kubernetes

The Sensors ► Collectors ► Sensor page displays a list of configured Sensor Collectors and their details.

On this page, you can:

• Search and filter the list using the top bar
• Sort the list by clicking a column header
• View more details by clicking a row

View Sensor Collector details

From the list, click a Sensor Collector row to view more details. The right sidebar appears, showing a Summary view.

Click the Configuration tab to view and manage configuration details.

When more information is available, expand Details to see more details.

Create a Sensor Collector configuration

To create a Sensor Collector configuration:

1. Click + on the upper right.
   The New Sensor Collector modal appears.
   
2. Select the Sensor Collector type (Gateway or CSV), then click Configure sensor collector.
3. Enter the details.
   Metric configuration (for Gateway type): this refers to pre-provisioned configurations, which are used to align incoming data into metrics for consumption in the application.
4. Click ✓ to save the changes.

Update a Sensor Collector configuration

To update a Sensor Collector configuration:

1. From the list, click a Sensor Collector row.
   The right sidebar appears, showing a Summary view.
2. Click the Configuration tab.
3. Make the required changes.
   Type and Metric configuration cannot be updated.
4. Click ✓ to save the changes.

Download the collector image

Download the collector image for Docker or Kubernetes.

To download the collector image:

1. Click the Sensor Collector row from the list. The right sidebar displays.
2. Click the ellipsis on the upper right, the click the applicable option:
   • Download (Docker)
   • Download (Kubernetes)

Delete a Sensor Collector configuration

To delete a Sensor Collector configuration:

1. Click the Sensor Collector row from the list. The right sidebar displays.
2. Click the ellipsis on the upper right, the click Delete.
3. Click Delete to confirm the action.

Metric configuration

For Gateway type Sensor Collector configurations, select the Metric configuration, which refers to pre-provisioned configurations that are used to align incoming data into metrics for consumption in the application.

Available parameters include:

• Metric configuration version *
• Session filter profile ID
• Availability zone *
• Metric gateway port
• Management proxy port

flex

Acts as a data broker for Cisco Provider Connectivity Assurance Sensors F25 and F100 (formerly Skylight performance elements Flex family).

As a data broker, the connector acts as the local receiver of data from F25 and F100 Sensors. The connectors are deployed closer to the element/edge but still with connectivity back to the Cisco Provider Connectivity Assurance service, which is more likely to be provisioned centrally or in a public cloud.

sensor-agent

Acts as both a management and data broker for Cisco Provider Connectivity Assurance Sensor Agents (formerly Skylight sensor: agents).

• As a management broker, the connector acts as a proxy between any connected Agents and the agent orchestrator that manages them. When Agents are provisioned, you provide the IP and port of the connector through which the Agents phone home for configuration.

• As a data broker, the connector acts as the local receiver of data from Agents. The connectors are deployed closer to the agents/edge but still with connectivity back to the Cisco Provider Connectivity Assurance service, which is more likely to be provisioned centrally or in a public cloud.