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
This PR adds support for scraping application level metrics straight
from the ECS nodes, without going through the load balancer, solving the
flapping behavior described in #104
To achieve this we had to solve the following problems:
- Reach the cluster nodes in AWS, this was solved by
#182
- Discover ECS tasks with their corresponding port and IP address. This
was a bit more tricky, we solved it by adding a cronjob that runs a
python script that will request ECS data from AWS using the `boto3`
client, and then storing that information into a [Prometheus file based
discovery](https://prometheus.io/docs/guides/file-sd/) compatible file
So, this PR will add:
- A Python script to collect ECS tasks information from aws and writing
it into a file
- An Ansible configuration for creating and running this file with a
cronjob
- An update to the Nginx configuration used to proxy metrics requests
from the monitoring host to the EC2 instances in AWS
- Security groups configuration to allow traffic from the proxy host to
the ECS cluster nodes
- IAM credentials used for requesting tasks information from AWS
This PR solves ooni/backend#937 and
ooni/backend#938 and is related to
#104
After #937 is done, we have to:
The text was updated successfully, but these errors were encountered: