Use our own fork of gds_metrics_python and add shared auth token

This will allow both prometheis (the shared one and our own) to scrape
the /metrics endpoint, each with their own authentication

See alphagov/gds_metrics_python#1 for more details
This commit is contained in:
sakisv
2022-04-21 15:30:03 +03:00
parent cc5af6fabb
commit 76b9e28d4d
3 changed files with 3 additions and 2 deletions

View File

@@ -49,6 +49,7 @@ applications:
SECRET_KEY: '{{ SECRET_KEY }}'
ROUTE_SECRET_KEY_1: '{{ ROUTE_SECRET_KEY_1 }}'
ROUTE_SECRET_KEY_2: '{{ ROUTE_SECRET_KEY_2 }}'
METRICS_BASIC_AUTH_TOKEN: {{ METRICS_BASIC_AUTH_TOKEN }}
AWS_ACCESS_KEY_ID: '{{ AWS_ACCESS_KEY_ID }}'
AWS_SECRET_ACCESS_KEY: '{{ AWS_SECRET_ACCESS_KEY }}'

View File

@@ -33,4 +33,4 @@ govuk-frontend-jinja @ git+https://github.com/alphagov/govuk-frontend-jinja.git@
# gds-metrics requires prometheseus 0.2.0, override that requirement as later versions bring significant performance gains
prometheus-client==0.14.0
gds-metrics==0.2.4
git+https://github.com/alphagov/gds_metrics_python.git@6f1840a57b6fb1ee40b7e84f2f18ec229de8aa72

View File

@@ -67,7 +67,7 @@ flask-redis==0.4.0
# via notifications-utils
flask-wtf==1.0.1
# via -r requirements.in
gds-metrics==0.2.4
gds-metrics @ git+https://github.com/alphagov/gds_metrics_python.git@6f1840a57b6fb1ee40b7e84f2f18ec229de8aa72
# via -r requirements.in
geojson==2.5.0
# via notifications-utils