Good morning,
I am seeing an issue when adding a limit configuration to my promtail configuration file. We have some rather large servers that we need to install promtail on but installing and enabling promtail would instantly overload the promtail server with our log ingestion. I researched into different methods of limiting the logs that are sent through but my approach doesn’t seem to work. Here is my configuration, and below that is the error I’m receiving:
I’m running the OSS version of Grafana. I just need a recommendation on what configuration block I can use in my promtail configuration to limit the rate of log ingestion sent out and into my Loki server. I use Grafana to visualize these logs sent to Loki.
When I run promtail on a large server without a limit config, I am facing downtime on my server. For Loki/Promtail v2.9.5, what is a good log limit configuration I can use in my promtail configuration?
Something like this:
server:
http_listen_port: 9080
grpc_listen_port: 0
positions:
filename: /tmp/positions.yaml
clients:
- url: http://test.com:3100/loki/api/v1/push
scrape_configs:
- job_name: provider
static_configs:
- targets:
- localhost
labels:
job: providerlogs
__path__: /opt/xxx/xxx/log/xxx.log
server: xxx-app
- limit:
rate: 10
burst: 10
For me it returns this error and I’m not sure if it’s just not valid to use anymore, and if not what is a good substitute?
The error:
Unable to parse config: /etc/promtail/promtail-local-config.yaml: yaml: unmarshal errors:
promtail-linux-amd64: line 53: field limit not found in type scrapeconfig.plain
Thanks!