Reviewed on 02 April 2024 • Published on 10 January 2023
This page explains how to configure the Grafana agent and the Zipkin collector to push your metrics, logs, and traces. You can use it to push your data from Scaleway resources or external resources.
Having the default configuration on your agents might lead to more of your resources’ metrics being sent, a high consumption and a high bill at the end of the month.
Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the product pricing for more information.
It is not currently possible to collect logs if you are using OSX.
Create a token and select the push permission for metrics, traces, and logs.
Create a folder where you will keep your configuration files.
Create a configuration file inside your folder and name it config.yaml. This file will contain the Grafana agent configuration.
Copy the following YAML template.
Important
Make sure you replace <your metrics push url> with https://metrics.cockpit.fr-par.scw.cloud/api/v1/push, <your logs push url> with https://logs.cockpit.fr-par.scw.cloud/loki/api/v1/push and <your traces push url> with https://traces.cockpit.fr-par.scw.cloud/otlp
Make sure you replace <your metrics push token>, <your logs push token> and <your traces push token> with the token you created in step 1
metrics:
wal_directory: /tmp/agent
global:
scrape_interval: 60s
remote_write:
- url: <your metrics push url>
headers:
"X-Token": <your metrics push token>
logs:
positions_directory: /tmp/positions/
configs:
- name: scw
clients:
- url: <your logs push url>
tenant_id: <your logs push token>
scrape_configs:
- job_name: varlogs
static_configs:
- targets: [localhost]
labels:
job: varlogs
__path__: /host/root/var/log/*.log
traces:
configs:
- name: default
remote_write:
- endpoint: <your traces push url>
headers:
X-TOKEN: <your traces push token>
protocol: http
format: otlp
receivers:
otlp:
protocols:
grpc:
http:
zipkin:
endpoint: 0.0.0.0:9411
integrations:
node_exporter:
enabled: true
rootfs_path: /host/root
sysfs_path: /host/sys
procfs_path: /host/proc
# Anything not provided in the list below will be disabled by default
set_collectors:
- uname
- cpu
- loadavg
- meminfo
- filesystem
- netdev
- boottime
- time
- stat
Your configuration file should look like the following:
Adding the ID of the data source to the endpoint. You can retrieve the ID of the data source you want to configure using the ListDataSources API command, or
Adding the X-Datasource-Id header in the headers section, under X-Token.
Important
If you do not specify a data source, your data will automatically be pushed to the default data source for the concerned data type.
Below is an example of what your Traces configuration should look like if you add the X-Datasource-Id header: