Enriching 3rd Party Data
groundcover supports setting key attributes in ingested data by using special HTTP / gRPC headers, or by using specific key-value attributes. This is especially relevant when using 3rd party integrations where the groundcover sensors is not present.
See each integration page for specific examples
List of Attributes
workload
service.name
x-groundcover-service-name
The name of the service or workload
env_type
gc_env_type
x-groundcover-env-type
The type of environment (e.g. k8s, VM)
env
env_name
x-groundcover-env-name
The environment (e.g prod, dev)
source
source
x-groundcover-source
Source of the data
cluster
cluster
x-groundcover-cluster
Associated cluster name
Priority and Precedence
When both resource attributes and headers are present:
Headers take precedence over resource attributes
If a header is not provided, the corresponding resource attribute will be used
If neither is provided - we'd try to deduce from other attibures if possible
Last updated