You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when k6 is doing remote writes into Prometheus, it does add a single label 'scenario'. When multiple k6 copies are run from multiple servers, they don't work together with a single Prometheus server.
It would be nice to be able to distinct different jobs in the Prometheus with different labels.
Suggested Solution (optional)
Add an environment variable (e.g. K6_PROMETHEUS_REMOTE_LABELS="environment=production,server=srv1") to specify list of labels to be set on the series send to the Prometheus.
Any other solution (e.g. configuration within js file) will solve the problem too.
The text was updated successfully, but these errors were encountered:
@amarao We ran into a similar problem in kubernetes. There is a way to add tags using command line flags so we inject the kubernetes pod ID as it's own tag. This eliminated the collision of data into one series.
Feature Description
Currently, when k6 is doing remote writes into Prometheus, it does add a single label 'scenario'. When multiple k6 copies are run from multiple servers, they don't work together with a single Prometheus server.
It would be nice to be able to distinct different jobs in the Prometheus with different labels.
Suggested Solution (optional)
Add an environment variable (e.g.
K6_PROMETHEUS_REMOTE_LABELS="environment=production,server=srv1"
) to specify list of labels to be set on the series send to the Prometheus.Any other solution (e.g. configuration within js file) will solve the problem too.
The text was updated successfully, but these errors were encountered: