VictoriaMetrics/lib/protoparser/newrelic
Aliaksandr Valialkin 2c334ed953
app/{vmagent,vminsert}: follow-up for NewRelic data ingestion protocol support
This is a follow-up for f60c08a7bd

Changes:

- Make sure all the urls related to NewRelic protocol start from /newrelic . Previously some urls were started from /api/v1/newrelic

- Remove /api/v1 part from NewRelic urls, since it has no sense

- Remove automatic transformation from CamelCase to snake_case for NewRelic labels and metric names,
  since it may complicate the transition from NewRelic to VictoriaMetrics. Preserve all the metric names and label names,
  so users could query metrics and labels by the same names which are used in NewRelic.
  The automatic transformation from CamelCase to snake_case can be added later as a special action for relabeling rules if needed.

- Properly update per-tenant data ingestion stats at app/vmagent/newrelic/request_handler.go . Previously it was always zero.

- Fix NewRelic urls in vmagent when multitenant data ingestion is enabled. Previously they were mistakenly started from `/`.

- Document NewRelic data ingestion url at docs/Cluster-VictoriaMetrics.md

- Remove superflouos memory allocations at lib/protoparser/newrelic

- Improve tests at lib/protoparser/newrelic/*

Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3520
Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/4712
2023-10-16 00:25:25 +02:00
..
stream app/{vmagent,vminsert}: follow-up for NewRelic data ingestion protocol support 2023-10-16 00:25:25 +02:00
parser.go app/{vmagent,vminsert}: follow-up for NewRelic data ingestion protocol support 2023-10-16 00:25:25 +02:00
parser_test.go app/{vmagent,vminsert}: follow-up for NewRelic data ingestion protocol support 2023-10-16 00:25:25 +02:00
parser_timing_test.go app/{vmagent,vminsert}: follow-up for NewRelic data ingestion protocol support 2023-10-16 00:25:25 +02:00