Aliaksandr Valialkin 3d75c39ff4 app/vlinsert/loki: follow-up for 3aeb1b96a2 ... - Disallow more than 3 items in Loki line entry, since it must contain two mandatory entries: timestamp and message, plus one optional entry - structured metadata. See https://grafana.com/docs/loki/latest/reference/loki-http-api/#ingest-logs - Update references to structured metadata docs in Loki, in order to simplify further maintenance of the code - Move the change from bugfix to feature at docs/VictoriaLogs/CHANGELOG.md, since VictoriaLogs never supported structured metadata over JSON Loki protocol. The support for structured metadata in protobuf Loki protocol has been added in ac06569c49 , which has been included in v0.28.0-victorialogs. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7431 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/7432		2024-11-06 19:23:38 +01:00
..
loki.go	app/vlinsert/syslog: allow accepting syslog messages with different configs at different ports	2024-06-17 23:16:34 +02:00
loki_json.go	app/vlinsert/loki: follow-up for 3aeb1b96a2	2024-11-06 19:23:38 +01:00
loki_json_test.go	app/vlinsert/loki: follow-up for 3aeb1b96a2	2024-11-06 19:23:38 +01:00
loki_json_timing_test.go	app/vlinsert: properly parse length-delimited syslog messages sent over TCP according to RFC5425	2024-06-17 22:28:26 +02:00
loki_protobuf.go	app/vlinsert/loki: use easyproto instead for parsing Loki protobuf messages	2024-07-10 03:05:17 +02:00
loki_protobuf_test.go	app/vlinsert/loki: use easyproto instead for parsing Loki protobuf messages	2024-07-10 03:05:17 +02:00
loki_protobuf_timing_test.go	app/vlinsert/loki: use easyproto instead for parsing Loki protobuf messages	2024-07-10 03:05:17 +02:00
pb.go	app/vlinsert/loki: follow-up for 3aeb1b96a2	2024-11-06 19:23:38 +01:00