Integrating with Telemetry Data Collectors
The flow diagram illustrates a typical use case for configuring a data collector. The flow begins with the creation of a stream, followed by the subscription to that stream. Once subscribed, the user attaches assets to the stream, ensuring that the relevant event messages are captured. Optionally, the user can create alert rules to define specific conditions for triggering notifications or actions based on the event data. This flow represents a streamlined approach to configuring the data collector for event monitoring and management.
Data Collector Setup
You can collect event or metric data using various Sink Types, each designed to streamline data handling and processing. These Sink Types enable you to direct your data to preferred destinations.
Here's a list of what we support:
| Sink Type | Data Type - Event | Data Type - Metric |
|---|---|---|
| Datadog | Supported | Supported |
| Google Pub/Sub | Supported | Supported |
| Pager Duty | Supported | Not Supported |
| Service Now | Supported | Not Supported |
| Splunk HEC | Supported | Supported |
| Webhooks | Supported | Supported |
| Webhook - Grafana | Supported | Supported |
| Webhook - Microsoft Teams | Supported | Supported |
| Webhook - Slack | Supported | Supported |
Datadog
If you use Datadog as your data collector, provide your Datadog API and Application Keys when creating your subscription.
Google Pub/Sub
- Create a Topic
- Grant IAM permissions to a Service Account for Pub/Sub
- Provide your topic URI and your service account credentials when creating your subscription.
Pager Duty
If you are using Pager Duty as your data collector, create a service and an Events APIv2 integration to handle your events. Provide your Pager Duty URI and the Integration Key when creating your subscription.
Splunk
If you are using Splunk as your data collector, create an event index to receive events, a metrics index to receive metrics or both, then create an HTTP Event Collector. Provide your HTTP Event Collector URI, your HTTP Event Collector token, and the names of your indices when creating your subscription
Webhooks
If you use a service that allows streaming in data from a webhook, you can create a webhook subscription with sink type WEBHOOK for both events and metrics.
Microsoft Teams - If you are using a Microsoft Teams channel as your data collector, create and configure a webhook to post messages when a webhook request is received. Once your webhook is configured, provide your HTTP POST URL when creating your subscription.
Slack - If you are using Slack as your data collector, create and configure a Slack App for incoming webhooks. Provide your webhook's unique URL when creating your subscription.