Feat: Add prometheus remote write support#2800
Draft
svenvg93 wants to merge 3 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Important
should be updated and verified after #2802
📃 Description
Adds Prometheus Remote Write support, allowing speedtest metrics to be pushed directly to a remote write endpoint after each speedtest completes. Compatible with Prometheus, VictoriaMetrics, Grafana Cloud (Mimir), and Cortex.
The Prometheus settings tab has been reorganised into two sections: Scrape Endpoint (existing pull-based setup) and Remote Write (new push-based setup).
📖 Documentation
TBD
🪵 Changelog
➕ Added
PrometheusRemoteWriteServiceto build and send Protobuf-encoded payloads compressed with SnappyApp\Jobs\Prometheus\WriteResultjob to dispatch remote write asynchronously via the queueprometheus_remote_write_*keys to thedataintegrationgroup➕ New dependency
The Prometheus Remote Write protocol (spec) mandates that the protobuf payload is compressed with Snappy before sending. The Content-Encoding: snappy header is required — endpoints that implement the spec strictly (including self-hosted Prometheus with --enable-feature=remote-write-receiver) will reject requests with any other encoding, returning a 415 Unsupported Media Type error.
PHP has no built-in Snappy support (unlike gzip via gzencode()), and the only alternative — the ext-snappy PECL extension — requires compiling a native PHP extension into the Docker image, which would complicate the deployment significantly.
flow-php/snappy(^0.38.0) is a pure-PHP implementation of the Snappy algorithm that works without any PHP extension.✏️ Changed
PrometheusMetricsServiceandPrometheusRemoteWriteServicemoved toApp\Services\Prometheus\to align with the existingApp\Jobs\Prometheus\namespaceProcessSpeedtestDataIntegrationslistener now dispatchesWriteResultjob when remote write is enabled