Monitor Data Sources Integrations
Overview
groundcover supports many types of data sources that could be integrated. Once an integration is live, users can evaluate whether the integration is working as expected.
This page details the various methods that users can apply in order to better understand their integrations status.
Pull Integrations
In the case of pull integrations, groundcover runs every interval and pulls information from an external data source. The following are examples of pull integrations - AWS CloudWatch, GCP Metrics, Prometheus, Redis Cloud.
All of the pull integrations are defined in the data sources page.
The following information is available for users by clicking on any configuration and opening the drawer:
Stats - The number of metrics pulled and which metrics are pulled.
Activity status - the status of each attempt to collect data, such as authentication failure.
Stats
This information is available in the Stats tab.
The top chart shows a bar for every collection run and indicates the number of entries collected in a specific run.
The bottom table details the specific metrics that were collected and their level of cardinality.
Users can change the time frame in order to see changes over time and see metrics which are collected in lower frequency.
Additional option is to navigate to the Data Explorer page, focus on a specific metric and apply a filter by gc_integration_name to see trends related to that metric.
Activity Traces
Open the drawer and navigate to the Activity Traces tab to see the list of traces. Each row represent a single run to collect data.
Similarly, users can navigate to the Traces page and apply a filter by source:groundcover-platform gc_integration_name::<your integration name>. For example, the above integration can be searched by applying the following filter - source:groundcover-platform gc_integration_name:"Prometheus Integration"
Push Integrations
In the case of push integrations, users should check the source for any issues sending data. Within groundcover, any label that was added to incoming Telemetry can be used to filter accordingly and ensure the right data is sent.
Last updated