6 commits

Author	SHA1	Message	Date
Roman Khavronenko	cd1aca217c	lib/protoparser/opentelemetry/firehose: escape requestID before returning it to user (#6451) ... All user input should be sanitized before rendering. This should prevent possible attacks. See https://github.com/VictoriaMetrics/VictoriaMetrics/security/code-scanning/203 Signed-off-by: hagen1778 <roman@victoriametrics.com>	2024-06-10 16:55:59 +02:00
Aliaksandr Valialkin	904e95fc69	app/vmagent: simplify code after 509df44d03 ... - Simplify the code in order to improve its maintenance - Properly pass tenant ID when processing multi-tenant opentelemetry request at vmagent Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6016	2024-04-02 17:58:13 +03:00
Andrii Chubatiuk	509df44d03	app/{vmagent,vminsert}: fixed firehose response (#6016)	2024-03-26 13:20:41 +01: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