Connector Configuration

Overview

Manage connector configurations by using the Settings ► Connectors page.

Connector configurations define the data collection parameters based on the data source required. The data source can be Accedian Sensors or third-party sources. Once you have set up your connector, you can use it to download Roadrunner with the connector configuration already included and ready to deploy.

See Deploying Roadrunner in Docker for a walkthrough of collector configuration and deployment.

Creating a Connector Configuration

To create a connector configuration:

1. Go to Settings ► Connectors.
2. Click + in the top-right. The New connector configuration sidebar displays.

3. Configure the required parameters.

   For each connector, enter a Name and select a Datasource type:

   • Data Gateway - flex
   • Data Gateway - sensor-agent
   • CiscoTelemetry
   • FileWatcher

   Connectors require a unique Zone value, which Skylight performance analytics uses internally to track the connector status and the data received from it.

4. Click ✓ to save your changes.

Updating a Connector Configuration

To update a connector configuration:

1. Go to Settings ► Connectors.
2. Click the row for the connector. The Connector summary sidebar displays.
3. Configure the parameters as needed.
4. Click ✓ to save your changes.

Tip: Clicking the x icon resets, and does not close, the Connector summary form.

Datasource Types and Parameters

This section describes the different datasource types and the parameters available for each. An asterisk (*) denotes a required field that cannot be empty.

Data Gateway - flex

Acts as a data broker for Skylight Flex.

As a data broker, the connector acts as the local receiver of data from Flex performance elements. The connectors are deployed closer to the element/edge but still with connectivity back to the Skylight performance analytics service, which is more likely to be provisioned centrally or in a public cloud.

Available parameters include:

• Version *
• Session filter profile ID
• Zone *
• Metric gateway port
• Management proxy port

Data Gateway - sensor-agent

Acts as both a management and data broker for 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 configuation.
• 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 Skylight performance analytics service, which is more likely to be provisioned centrally or in a public cloud.

Available parameters include:

• Version *
• Session filter profile ID
• Zone *
• Metric gateway port
• Management proxy port

CiscoTelemetry

Used for integrating Cisco devices supporting Model-Driven Telemetry (MDT).

The URL and Port parameters refer to the location that the connector will attempt to register to receive data.

Available parameters include:

• Session filter profile ID
• Zone *
• URL *
• Port

FileWatcher

Used by most Accedian data sources, especially for cases where data is coming from Skylight orchestrator. The Path refers to the full file path that the connector will "watch" for new data files. The connector will constantly poll this directory for new Accedian .csv data files, parse them, and upload their contents to Skylight performance analytics. Once uploaded, these files will be removed.

Available parameters include:

• Session filter profile ID
• Zone *
• Path *

See Creating and Installing Roadrunner for Skylight orchestrator for more information.

Others

Other datasource types may also be available.

OpenMetrics Scraper

Used for collecting data from third-party sources (as part of Accedian Professional Service engagements). Only provisionable via API.

PVXWatcher

Represents the embedded connectors used by Skylight capture sensor.