VictoriaMetrics/lib/protoparser/prometheus
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
..
stream lib/protoparser: substitute hybrid channel-based pools with plain sync.Pool 2024-04-20 21:59:51 +02:00
parser.go Revert "Exemplar support (#5982)" 2024-07-03 15:30:21 +02:00
parser_test.go Revert "Exemplar support (#5982)" 2024-07-03 15:30:21 +02:00
parser_timing_test.go Revert "Exemplar support (#5982)" 2024-07-03 15:30:21 +02:00
util.go lib/prompbmarshal: move MustParsePromMetrics to protoparser/prometheus (#8405) 2025-02-27 22:50:27 +01:00