WIP: [translator/prometheusremotewrite] Expose PrometheusConverter type, with generated implementation #32665
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Expose the
PrometheusConverter
type frompkg/translator/prometheusremotewrite
(previosly hidden behind the wrappingFromMetrics
function), and generate thePrometheusConverter.FromMetrics
implementation from templates. This approach lets Prometheus compatible systems such as Grafana Mimir, Thanos, Cortex etc. generate translation code for their own target format.Also use the
PrometheusConverter
type fromexporter/prometheusremotewriteexporter
, to avoid the overhead of unnecessary translation inprometheusremotewrite.FromMetrics
.Link to tracking Issue: #32666
Testing:
I've benchmarked, the results are: TODO
Documentation: