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
We can monitor ECS tasks with a Prometheus thanks to this scraping config, but unfortunately we need a different job for both prod and dev because of the basic auth section, the password is different in dev and prod.
In order to scrape metrics for both prod and dev, we would have to create a different job for each environment, duplicating a lot of code
So a possible solution would be to use the same password for both prod and dev (see #186 (comment))
The final result should:
have a single job block with all the required settings to scrape ECS tasks, both from prod and dev
allow differentiating the environment with a Prometheus label (environment = dev for example)
The text was updated successfully, but these errors were encountered:
We can monitor ECS tasks with a Prometheus thanks to this scraping config, but unfortunately we need a different job for both prod and dev because of the basic auth section, the password is different in dev and prod.
In order to scrape metrics for both prod and dev, we would have to create a different job for each environment, duplicating a lot of code
So a possible solution would be to use the same password for both prod and dev (see #186 (comment))
The final result should:
environment = dev
for example)The text was updated successfully, but these errors were encountered: