There are a few instances where this might be helpful: Promtail can also be configured to receive logs from another Promtail or any Loki client by exposing the Loki Push API with the loki_push_api scrape config. Refer to the docs forĬonfiguring Promtail for more details. Relabel_configs allows for fine-grained control of what to ingest, what toĭrop, and the final metadata to attach to the log line. Just like Prometheus, promtail is configured using a scrape_configs stanza. Kubernetes API server while static usually covers all other use cases. kubernetes service discovery fetches required labels from the This limitation is due to the fact that Promtail is deployed as aĭaemon to every local machine and, as such, does not discover label from other Service discovery mechanism from Prometheus,Īlthough it currently only supports static and kubernetes serviceĭiscovery.
Specifically, this means discoveringĪpplications emitting log lines to files that need to be monitored.
Log file discoveryīefore Promtail can ship any data from log files to Loki, it needs to find out Systemd journal (on AMD64 machines only). Promtail is an agent which ships the contents of local logs to a private Grafana Lokiĭeployed to every machine that has applications needed to be monitored.Ĭurrently, Promtail can tail logs from two sources: local log files and the
0 kommentar(er)
