letsencrypt / ct-woodpecker / 530 / 1
69%
main: 68%

LAST BUILD BRANCH: master
DEFAULT BRANCH: main
Ran
Files 12
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 67.809%. Remained the same
GO111MODULE=on

push

travis-ci

web-flow 
docker-compose: ct-test-srv, ct-woodpecker, prometheus, alertmanager. (#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 https://github.com/letsencrypt/ct-woodpecker/pull/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... (continued)

811 of 1196 relevant lines covered (67.81%)

4.4 hits per line

Source Files on job 530.1 (GO111MODULE=on)