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 we don't have observability into the container host of the ECS cluster. Moreover we are only able to scrape aggregate metrics from the services that are behind the balancer, which means we end up with the metrics "flapping".
Ideally we would have a way of scraping metrics for the container host, but also the per-servicer docker containers.
In summary we would like to collect two classes of metrics:
Host container metrics (the ec2 nodes that run docker and we deploy docker containers to), using node_exporter
Docker container application metrics, which are exposed using the instrumentator and we would like to scrape independently per each host container
The text was updated successfully, but these errors were encountered:
The problem I'm seeing right now is that the monitor server is not in AWS, so we have some issues with the connection between that server and the ec2 instances:
We have to set up IAM credentials for the server, as mentioned in the link above
The prometheus server needs a way to reach the ec2 instances (not the load balancer), but they're probably not open to internet traffic (and I don't think they should), what can we do about this?
Currently we don't have observability into the container host of the ECS cluster. Moreover we are only able to scrape aggregate metrics from the services that are behind the balancer, which means we end up with the metrics "flapping".
Ideally we would have a way of scraping metrics for the container host, but also the per-servicer docker containers.
In summary we would like to collect two classes of metrics:
node_exporter
The text was updated successfully, but these errors were encountered: