Ingestion Endpoints
Last updated
Last updated
Our inCloud Managed backend supports ingestion of various standard formats for metrics, traces and logs. It can be used to ingest telemetry from outside your kubernetes clusters, displaying it natively inside the groundcover platform.
Every ingestion endpoint below requires two things:
inCloud site - the installation domain specific to your backend
api-key - used to authenticate with your backend
Your inCloud site is part of the configuration provided to you by groundcover when setting up the managed inCloud backend. It can be located in the installation values, marked below as {inCloud_Site}
:
The api-key used to ingest data into groundcover can be recovered using our built in CLI, using the following command:
The api-key printed will be referenced below as {api-key}
We support several methods of authentication when pushing data into groundcover. This applies for all endpoints, formats and protocols.
Add a header with one of the following keys, containing the {api-key}
value:
token
apikey
dd-api-key
X-Amz-Firehose-Access-Key
Authorization
When using basic authentication, use the following params:
Username: groundcover
Password: {api-key}
Prometheus remote write
https://{inCloud_Site}/api/v1/write
Prometheus exposition format
https://{inCloud_Site}/api/v1/import/prometheus
gRPC (Logs, Traces, Metrics)
{inCloud_Site}
HTTP Logs
https://{inCloud_Site}/v1/logs
HTTP Traces
https://{inCloud_Site}/v1/traces
HTTP Metrics
https://{inCloud_Site}/v1/metrics
Metrics V1
https://{inCloud_Site}/datadog/api/v1/series
Metrics V2
https://{inCloud_Site}/datadog/api/v2/series
Traces V0.3
https://{inCloud_Site}/v0.3/traces
Traces V0.4
https://{inCloud_Site}/v0.4/traces
Traces V0.5
https://{inCloud_Site}/v0.5/traces
Traces V0.7
https://{inCloud_Site}/v0.7/traces
Firehose Logs
https://{inCloud_Site}/firehose/logs
JSON Logs
https://{inCloud_Site}/json/logs