4 commits

Author	SHA1	Message	Date
Andrii Chubatiuk	01430a155c	vlinsert: added opentelemetry logs support ... Commit adds the following changes: * Adds support of OpenTelemetry logs for Victoria Logs with protobuf encoded messages * json encoding is not supported for the following reasons: - It brings a lot of fragile code, which works inefficiently. - json encoding is impossible to use with language SDK. * splits metrics and logs structures at lib/protoparser/opentelemetry/pb package. * adds docs with examples for opentelemetry logs. --- Related issue: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4839 Co-authored-by: AndrewChubatiuk <andrew.chubatiuk@gmail.com> Co-authored-by: f41gh7 <nik@victoriametrics.com>	2024-09-03 20:12:05 +02:00
Aliaksandr Valialkin	5aa3dfbd20	lib/protoparser/opentelemetry/firehose: verify that the full response is parsed properly in ProcessRequestBody ... This is a follow-up for bf9cb84575 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5899	2024-03-01 00:39:10 +02:00
Andrii Chubatiuk	bf9cb84575	opentelemetry: fix firehose message parsing (#5899) ... Co-authored-by: Andrii Chubatiuk <wachy@Andriis-MBP-2.lan>	2024-03-01 00:23:54 +02:00
Aliaksandr Valialkin	04d13f6149	app/{vminsert,vmagent}: follow-up after 67a55b89a4 ... - Document the ability to read OpenTelemetry data from Amazon Firehose at docs/CHANGELOG.md - Simplify parsing Firehose data. There is no need in trying to optimize the parsing with fastjson and byte slice tricks, since OpenTelemetry protocol is really slooow because of over-engineering. It is better to write clear code for better maintanability in the future. - Move Firehose parser from /lib/protoparser/firehose to lib/protoparser/opentelemetry/firehose, since it is used only by opentelemetry parser. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5893	2024-02-29 14:38:23 +02:00

Renamed from lib/protoparser/firehose/parser_test.go (Browse further)