Build ontop of cpu-docker-compose #77
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
pgporada
commented
Dec 19, 2018
pgporada
commented
- Updated the grafana dashboard to match the picture in examples. This was mistakenly missed by me.
- Added grafana and related configs so it's plug and play with docker-compose.
…docker-compose. Added grafana configs.
cpu
approved these changes
Dec 19, 2018
There was a problem hiding this comment.
This is really cool, thanks @pgporada 👍 Once #76 is reviewed and merged I'll merge this (assuming there isn't any required feedback that cascades into this PR)
Is setting the providers.options.path to /etc/grafana/provisioning/dashboards all that it took to get Grafana to automatically add the dashboard JSON? Very handy!
|
@pgporada Can you pull |
Grafana v5 allows someone to place a dashboard json file in a specified path and Grafana will automatically |
…er into phil-docker-compose
…#76) This adds docker support for building images for `ct-test-srv`, `ct-woodpecker`, and `ct-malformed`, and an end-to-end environment for testing `ct-woodpecker` and Prometheus alerts backed by its metrics. The provided `docker-compose.yml` can be used to create a `ct-test-srv` container providing two certificate transparency logs `log-one` and `log-two`. A `ct-woodpecker` container is configured to monitor both logs storing the data in the mounted sqlite3 db `storage.sqlite`. A `prometheus` container is configured to scrape the `ct-woodpecker` container metrics, and to use an `alertmanager` container to process any alerts. For now the `alertmanager` container uses an `/echo` endpoint on one of the `ct-test-srv` logs as a webhook POST target so that alerts are printed to stdout via the `ct-test-srv`. The `prometheus` container comes configured with the alerts from #70 as a starting-point (thanks @pgporada!) To allow testing alert rules the `ct-test-srv` now has a way to add generic mock responses for any path. This can be used (for e.g.) to configure one of the logs to return a 500 error for `/ct/v1/add-chain` for a period of time. To use the docker environment, first make sure you have a `storage.sqlite` db created in the project root: `rm storage.sqlite 2>/dev/null ; cat storage/schema.sqlite | sqlite3 ./storage.sqlite` Then start the containers: `docker-compose up` You can access Prometheus at: `http://localhost:9090` You can break certificate submission for `log-two` by running: `curl -X POST -d '{"path":"/ct/v1/add-chain","code":404,"response":{"error":"oh noes!"}}' localhost:4601/add-mock` Shortly afterwards (2-4m) you can expect the `CertSubmissionErrors` alert to be firing in `http://localhost:9090/alerts` based on the `ct-woodpecker` container being unable to submit certificates to `log-two`. You can cause the alert to recover by fixing `log-two`'s certificate submission by running: `curl -X POST -d '{"path":"/ct/v1/add-chain"}' localhost:4601/clear-mock` Prometheus scrape data will be maintained in Docker volume called `ct-woodpecker_prometheus_data`. If you remove your docker-compose containers make sure to also `docker volume rm ct-woodpecker_prometheus_data` to reset the Prometheus data volume.
|
I did not notice that this merged into |
cpu
pushed a commit
that referenced
this pull request
Jan 7, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.