Zhu Jiekun e113a40142 app/vlinisert/loki: properly parse json logs with structured metadata ... Loki protocol supports optional `metadata` object for each ingested line. It's added as 3rd field at the (ts,msg,metadata) tuple. Previously, loki request json parsers rejected log line if tuple size != 2. This commit allows optional tuple field. It parses it as json object and adds it as log metadata fields to the log message stream. related issue: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7431 --------- Co-authored-by: f41gh7 <nik@victoriametrics.com> (cherry picked from commit 3aeb1b96a2)		2024-11-07 13:00:18 +01:00
..
loki.go	app/vlinsert/syslog: allow accepting syslog messages with different configs at different ports	2024-06-17 23:16:58 +02:00
loki_json.go	app/vlinisert/loki: properly parse json logs with structured metadata	2024-11-07 13:00:18 +01:00
loki_json_test.go	app/vlinisert/loki: properly parse json logs with structured metadata	2024-11-07 13:00:18 +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:30:28 +02:00
loki_protobuf.go	app/vlinsert/loki: use easyproto instead for parsing Loki protobuf messages	2024-07-10 03:05:55 +02:00
loki_protobuf_test.go	app/vlinsert/loki: use easyproto instead for parsing Loki protobuf messages	2024-07-10 03:05:55 +02:00
loki_protobuf_timing_test.go	app/vlinsert/loki: use easyproto instead for parsing Loki protobuf messages	2024-07-10 03:05:55 +02:00
pb.go	app/vlinsert/loki: use easyproto instead for parsing Loki protobuf messages	2024-07-10 03:05:55 +02:00