docker-based demonstration of an observability platform for titiler #1
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.
My goal with this repo is to demonstrate how to connect a TiTiler application to an observability backend (grafana). Right now it is just a docker network, so it will require a bit more digging to implement something similar in a deployed context. @ividito has done some related work over in eoapi-k8s. I wanted to show how you can have a more intelligent logging backend than just an endless stream in CloudWatch, how you can correlate logs to trace ids, etc. This gets part of the way there (no easy link to actual traces/spans from the logging statements yet) but I think the pipes are pretty much hooked up to make it possible. Grafana makes it easy to filter logs on attribute values like trace id, though.
I also added a document to summarize what I have learned about adding telemetry to applications over the last few weeks (resolves NASA-IMPACT/veda-odd#193) as well as some fairly speculative and sweeping generalizations about the impacts on performance in deployments that Claude helped me summarize. I want to test all of that out with our titiler-cmr deployment.