Merged
Conversation
Add support for tiled CT logs
reported in #91
Previously, metrics only reflected logs that were present at the initial start of the server. In order to track all the logs watched by certstream, each new log watcher must register with the prometheus metrics. The whole prometheus metrics logic was rewritten to be centered around a PrometheusExporter struct. The logmetrics file is moved to the metrics package in order to remove import dependencies. Also the prometheus file now relies stronger on dependency injection/callback functions. That prevents issues regarding circular imports. Also that prevents expensive nested loops to obtain certain data, since each metric now calls a single callback function to obtain the relevant data. fixes #96
This can be reintroduced with slog as debug output.
The wrong tags broke the links to the git commit comparison.
Seemingly, the sample config file is often used by default. Hence it should not only show off what's possible but also default to sane values. Adding unnecessary additional logs is not sane, so I removed it.
BREAKING CHANGE! Before this change, we had to map the config and index file (for the recovery feature) individually in order to persist current download progress. This also prevents permission issues regarding the ct_index file. Also this commit adds a config.docker.yml in order to have more control over the specific default config for docker containers.
If the baseURL already contains a slash in the end, another slash will be appended which leads to 403 errors.
When using the -create-index-file CLI parameter, previously the latest checkpoint size was not stored in the ct-index file.
fixes #67 Using viper gives us the ability to override options via environment variables. This means that I don't need to provide a config file but can configure the tool fully via env vars. This is especially useful for docker setups.
With `certstream-server-go validate` you can validate a config file before starting the server.
Previously ctIndex was always >= 0, and hence this always evaluated to true. Until we have a better solution, we should just ignore the value of ctIndex at all for the decision whether to continue downloading from a specific point.
This was referenced Apr 3, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.