Log in|Try sandbox

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

OpenTelemetry

DataDog

AWS Firehose

Last updated