Ingestion Endpoints

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.

Prerequisites

Every ingestion endpoint below requires two things:

  1. inCloud site - the installation domain specific to your backend

  2. api-key - used to authenticate with your backend

Fetching the inCloud site

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}:

global:
  ingress:
    site: {inCloud_Site}

Can't find your inCloud site value? Let us know over Slack.

Fetching the api-key

The api-key used to ingest data into groundcover can be recovered using our built in CLI, using the following command:

groundcover auth print-api-key

The api-key printed will be referenced below as {api-key}

Supported authentication methods

We support several methods of authentication when pushing data into groundcover. This applies for all endpoints, formats and protocols.

Header Key-Value

Add a header with one of the following keys, containing the {api-key} value:

  1. token

  2. apikey

  3. dd-api-key

  4. X-Amz-Firehose-Access-Key

  5. Authorization

Basic Authentication

When using basic authentication, use the following params:

Username: groundcover

Password: {api-key}

Supported endpoints

Prometheus

Name
Endpoint

Prometheus remote write

https://{inCloud_Site}/api/v1/write

Prometheus exposition format

https://{inCloud_Site}/api/v1/import/prometheus

OpenTelemetry

Name
Endpoint

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

DataDog

Name
Endpoint

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

AWS Firehose

Firehose ingestion requires setting up of a public endpoint, which was not available by default for inCloud Managed deployments provisioned before July 31st 2024.

Please contact us if your deployment is older in order to provision the needed endpoint.

Name
Endpoint

Firehose Logs

https://{inCloud_Site}/firehose/logs

Last updated