-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[development] Promremote storage local setup #3791
[development] Promremote storage local setup #3791
Conversation
96ee123
to
f9aa6ee
Compare
centai [coordinator] docker integration tests for prom-remote storage cleanup, wait for leader [development] Local Docker setup for prom-remote storage working config fix test revert
f9aa6ee
to
026f048
Compare
Codecov Report
@@ Coverage Diff @@
## master #3791 +/- ##
========================================
- Coverage 56.8% 56.8% -0.1%
========================================
Files 552 552
Lines 63077 63064 -13
========================================
- Hits 35888 35834 -54
- Misses 23986 24025 +39
- Partials 3203 3205 +2
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a few nits regarding indentation. Though I don't know all the intricacies of running M3 locally, and this applies even more for Prometheus.
ATTEMPTS=10 MAX_TIMEOUT=4 TIMEOUT=1 retry_with_backoff \ | ||
'curl -vvvsSf localhost:7201/health' | ||
|
||
echo "Running aggregator pipeline" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:
echo "Running aggregator pipeline" | |
echo "Running aggregator pipeline" |
M3AGGREGATOR_DEV_IMG=$(docker images m3aggregator:dev | fgrep -iv repository | wc -l | xargs) | ||
M3COLLECTOR_DEV_IMG=$(docker images m3collector:dev | fgrep -iv repository | wc -l | xargs) | ||
|
||
docker-compose -f docker-compose.yml up $DOCKER_ARGS etcd01 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:
docker-compose -f docker-compose.yml up $DOCKER_ARGS etcd01 | |
docker-compose -f docker-compose.yml up $DOCKER_ARGS etcd01 |
"consumerService": { | ||
"serviceId": { | ||
"name": "m3aggregator", | ||
"environment": "default_env", | ||
"zone": "embedded" | ||
}, | ||
"consumptionType": "REPLICATED", | ||
"messageTtlNanos": "600000000000" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:
"consumerService": { | |
"serviceId": { | |
"name": "m3aggregator", | |
"environment": "default_env", | |
"zone": "embedded" | |
}, | |
"consumptionType": "REPLICATED", | |
"messageTtlNanos": "600000000000" | |
} | |
"consumerService": { | |
"serviceId": { | |
"name": "m3aggregator", | |
"environment": "default_env", | |
"zone": "embedded" | |
}, | |
"consumptionType": "REPLICATED", | |
"messageTtlNanos": "600000000000" | |
} |
"consumerService": { | ||
"serviceId": { | ||
"name": "m3coordinator", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"consumerService": { | |
"serviceId": { | |
"name": "m3coordinator", | |
"consumerService": { | |
"serviceId": { | |
"name": "m3coordinator", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What this PR does / why we need it: Local dev setup to quickly test Prom Remote Write storage.
Special notes for your reviewer:
Refer to readme that describes this setup.
In order to generate some realistic metrics it's possible to scrape CAdvisor metrics from Kubernetes.
This is achieved by using
kubectl proxy
and the fact that each node exposes its metrics atlocalhost:8001/api/v1/nodes/${node}/proxy/metrics/cadvisor
.Does this PR introduce a user-facing and/or backwards incompatible change?:
Does this PR require updating code package or user-facing documentation?: