-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Prometheus integration to use remote writing #637
Comments
I think this is a good addition for distributed "attacks"! While we don't implement this, for distributed load tests an alternative would be:
We still will have some of the issues mentioned above, but it can help in the meanwhile. |
Would we implement this as part of the "attack" (changing the current implementation), or as a separate command? In both situations we have to be careful about the latency introduced by the push part, so probably we have to make it run asynchronously, in a separate goroutine from the main processes. What do you think? |
Sure, we'll have to be careful always when introducing changes to attack, this included! I'm leaning to change the existing implementation + introduce a separate prom-write sub-command. |
Just want to note that distributed tests shouldn't rely on an etcd server, or any other kind of external coordinator. |
Limitations of the current exporter based approach
Instead, we should do something like this: https://k6.io/docs/results-output/real-time/prometheus-remote-write/
The text was updated successfully, but these errors were encountered: