Caution
Grafana Agent has reached End-of-Life (EOL) on November 1, 2025. Agent is no longer receiving vendor support and will no longer receive security or bug fixes. Current users of Agent Static mode, Agent Flow mode, and Agent Operator should proceed with migrating to Grafana Alloy. If you have already migrated to Alloy, no further action is required. Read more about why we recommend migrating to Grafana Alloy.
Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
04 Logs and Traces
Logs and Traces can also be templated. This is built ontop of the previous examples.
docker run -v ${PWD}/:/etc/grafana grafana/agentctl:latest template-parse file:///etc/grafana/04_config.yml
Dynamic Configuration
Tells the Grafana Agent where to load files from.
Logs
Logs are loaded from a template matching logs-*.yml. There can ONLY be 1 template loaded
configs:
- name: test_logs
positions:
filename: /tmp/positions.yaml
scrape_configs:
- job_name: test
pipeline_stages:
- regex:
source: filename
expression: '\\temp\\Logs\\(?P<log_app>.+?)\\'configs:
- name: test_traces
automatic_logging:
backend: stdout
loki_name: default
spans: true


