VictoriaMetrics/docs/VictoriaLogs/data-ingestion/Promtail.md
Aliaksandr Valialkin 3b79f98459
Revert "docs victorialogs use relative links"
This reverts commit 3d7a77bf82.

Reason for revert: relative links do not work properly at GitHub code
and at GitHub wiki. For example, the following page contains broken links
before reverting this commit:

https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/docs/VictoriaLogs/CHANGELOG.md

It is always better to use absolute links thank relative links, since the page contents
can be copy-n-pasted to other pages, which are located in vastly different directories,
and all the links will remain working.
2023-10-16 14:03:21 +02:00

3.8 KiB

weight title disableToc menu aliases
4 Promtail setup true
docs
parent weight
victorialogs-data-ingestion 4
/VictoriaLogs/data-ingestion/Promtail.html

Promtail setup

Promtail is a default log shipper for Grafana Loki. Promtail can be configured to send the collected logs to VictoriaLogs according to the following docs.

Specify clients section in the configuration file for sending the collected logs to VictoriaLogs:

clients:
  - url: http://localhost:9428/insert/loki/api/v1/push?_stream_fields=instance,job,host,app

Substitute localhost:9428 address inside clients with the real TCP address of VictoriaLogs.

By default VictoriaLogs stores all the ingested logs into a single log stream. Storing all the logs in a single log stream may be not so efficient, so it is recommended to specify _stream_fields query arg with the list of labels, which uniquely identify log streams. There is no need in specifying all the labels Promtail generates there - it is usually enough specifying instance and job labels. See these docs for details.

See also these docs for details on other supported query args. There is no need in specifying _msg_field and _time_field query args, since VictoriaLogs automatically extracts log message and timestamp from the ingested Loki data.

It is recommended verifying whether the initial setup generates the needed log fields and uses the correct stream fields. This can be done by specifying debug parameter and inspecting VictoriaLogs logs then:

clients:
  - url: http://localhost:9428/insert/loki/api/v1/push?_stream_fields=instance,job,host,app&debug=1

If some log fields must be skipped during data ingestion, then they can be put into ignore_fields parameter. For example, the following config instructs VictoriaLogs to ignore filename and stream fields in the ingested logs:

clients:
  - url: http://localhost:9428/insert/loki/api/v1/push?_stream_fields=instance,job,host,app&ignore_fields=filename,stream

By default the ingested logs are stored in the (AccountID=0, ProjectID=0) tenant. If you need storing logs in other tenant, then specify the needed tenant via tenant_id field in the Loki client configuration The tenant_id must have AccountID:ProjectID format, where AccountID and ProjectID are arbitrary uint32 numbers. For example, the following config instructs VictoriaLogs to store logs in the (AccountID=12, ProjectID=34) tenant:

clients:
  - url: http://localhost:9428/insert/loki/api/v1/push?_stream_fields=instance,job,host,app&debug=1
    tenant_id: "12:34"

The ingested log entries can be queried according to these docs.

See also data ingestion troubleshooting docs.