FluentBit

groundcover automatically collects all logs within your Kubernetes cluster streamed via Standard Output (stdout) using our proprietary eBPF sensor, requiring no setup. However, if your organization stores logs in files, either within Kubernetes or outside, or if you want to pass logs from non-Kubernetes entities, you can use FluentBit to send these logs to groundcover.

We currently only supports ingesting logs from FluentBit. If you would like to suggest support for additional tools, let us know over Slack.

Setup instructions depend on whether your logs are stored in a Kubernetes or non-Kubernetes cluster.

Logs from inside a Kubernetes cluster

Finding the endpoint of our eBPF sensor's collector

First, direct FluentBit's OpenTelemetry Exporter to our eBPF sensor's daemonset.

Use the instructions here to locate the endpoint for the sensor service, referenced below as {GROUNDCOVER_SENSOR_ENDPOINT}.

Configuring an output stage

Add the following code to your FluentBit configuration file to start sending logs to groundcover:

[OUTPUT]
        Name opentelemetry
        Match *
        Host {GROUNDCOVER-SENSOR-ENDPOINT}
        Logs_uri /v1/logs
        Port 4318
        Tls Off
        Tls.verify Off
        Log_response_payload Off 
     

Logs from outside a Kubernetes cluster

This feature is only available for enterprise plan.

Finding the OTEL endpoint of the inCloud backend

The following example will use FluentBit's OpenTelemetry Exporter to send logs to your inCloud's endpoint.

For more instructions on finding your inCloud endpoint and apikey, see these docs.

Configuring an output stage

Add the following code to your Fluent Bit configuration to start sending logs to groundcover:

[OUTPUT]
        Name opentelemetry
        Match *
        Host {inCloud_Site}
        Logs_uri /v1/logs
        Port 443
        Tls On
        Tls.verify Off
        Log_response_payload Off
        Header apikey {api-key}
        
        # optional - This will allow you to label your logs under a specific environment.
        Header x-groundcover-env-name {env-name} 
        
        #  optional - This will allow you to label your logs under a specific env-type (i.e: ec2)
        Header x-groundcover-env-type {env-type}
   
        #  optional - This will allow you to label your logs under a specific service.
        Header x-groundcover-service-name {service-name}