VictoriaMetrics/app/vmagent/remotewrite
Roman Khavronenko 38d46d149f
lib/prompbmarshal: move MustParsePromMetrics to protoparser/prometheus (#8405)
`MustParsePromMetrics` imports `lib/protoparser/prometheus`, and this
package exposes the following metrics:
```
vm_protoparser_rows_read_total{type="promscrape"}
vm_rows_invalid_total{type="prometheus"}
```

It means every package that uses `lib/prompbmarshal` will start exposing
these metrics. For example, vlogs imports `lib/protoparser/common` which
uses `lib/prompbmarshal.Label`. And only because of this vlogs starts
exposing unrelated prometheus metrics on /metrics page.

Moving `MustParsePromMetrics` to `lib/protoparser/prometheus` seems like
the leas intrusive change.


-----------

Depends on another change
https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8403

Signed-off-by: hagen1778 <roman@victoriametrics.com>
2025-02-27 22:50:27 +01:00
..
client.go app/(vmagent,vmalert)/remotewrite/client: Fix flag docs (#7198) 2024-10-08 13:14:38 +02:00
client_test.go vmagent: remote write respect Retry-After in header (#6124) 2024-09-24 12:44:03 +02:00
pendingseries.go Revert "Exemplar support (#5982)" 2024-07-03 15:30:21 +02:00
pendingseries_test.go Revert "Exemplar support (#5982)" 2024-07-03 15:30:21 +02:00
pendingseries_timing_test.go lib/prompbmarshal: switch to github.com/VictoriaMetrics/easyproto 2024-01-14 23:04:45 +02:00
relabel.go all: consistently use 'any' instead of 'interface{}' 2024-07-10 00:20:37 +02:00
relabel_test.go app/vmagent/remotewrite: fix data race when extra labels are added to samples before sending them to multiple remote storage systems 2023-09-08 23:24:00 +02:00
remotewrite.go app/{vminsert,vmagent}: drop time series on exceeding labels limits. 2024-12-10 21:19:16 +01:00
remotewrite_test.go lib/prompbmarshal: move MustParsePromMetrics to protoparser/prometheus (#8405) 2025-02-27 22:50:27 +01:00
streamaggr.go lib/streamaggr: added aggregation windows (#6314) 2025-02-19 13:19:33 +01:00