Fluentd
Last updated
Last updated
groundcover supports ingestion of logs from Fluentd collectors. This page will guide you to configure your Fluentd collector to send logs it has collected to your groundcover installation.
While not required, it is suggested to set metadata attributes to be recognized by groundoover.
env_name
clusterId
Will associate the log with a cluster in groundcover.
host.name
Will appear as the logs' hostname
gc_source_type
will appear the source of the type of the logs. . Can be any value of your choosing. For example, logs from Kubernetes clusters are marked as 'k8s'
service.name
Will appear as the name of the workload that created the log.
For example:
Add this output plugin to your Fluentd configuration:
You can adjust further settings like buffer as described in the plugin's documentation.
source
can be used with the gc_source_type
attribute
env
can be used with the env_name
attribute
workload
can be used with the service.name
attribute
Will associate the log with an environment in groundcover.
We will use to send the logs to groundcover.
Use docs to find your inCloud's JSON logs endpoint, and make sure you have your API key. It should look something like this: https://<your-incloud-site>/json/logs
Access the groundcover and you should see your logs in the log page. We recommend looking based on the attributes previously set: