The syntax is the same what Prometheus uses. The topics is the list of topics Promtail will subscribe to. a list of all services known to the whole consul cluster when discovering Promtail can continue reading from the same location it left in case the Promtail instance is restarted. The most important part of each entry is the relabel_configs which are a list of operations which creates, The key will be. You will be asked to generate an API key. Prometheus Course They are set by the service discovery mechanism that provided the target I try many configurantions, but don't parse the timestamp or other labels. "https://www.foo.com/foo/168855/?offset=8625", # The source labels select values from existing labels. The nice thing is that labels come with their own Ad-hoc statistics. of streams created by Promtail. The jsonnet config explains with comments what each section is for. See the pipeline metric docs for more info on creating metrics from log content. of targets using a specified discovery method: Pipeline stages are used to transform log entries and their labels. Cannot retrieve contributors at this time. We and our partners use cookies to Store and/or access information on a device. their appearance in the configuration file. Prometheuss promtail configuration is done using a scrape_configs section. Configuring Promtail Promtail is configured in a YAML file (usually referred to as config.yaml) which contains information on the Promtail server, where positions are stored, and how to scrape logs from files. # Allow stale Consul results (see https://www.consul.io/api/features/consistency.html). # or decrement the metric's value by 1 respectively. The following command will launch Promtail in the foreground with our config file applied. log entry that will be stored by Loki.
