docs: eoAPI monitoring and logging design for the Operations BB (#202)#217
Draft
lhoupert wants to merge 1 commit into
Draft
docs: eoAPI monitoring and logging design for the Operations BB (#202)#217lhoupert wants to merge 1 commit into
lhoupert wants to merge 1 commit into
Conversation
1 task
96f0a28 to
123e9f9
Compare
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
123e9f9 to
0a140da
Compare
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
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.
Adds a one-page design note for the first increment of monitoring & logging integration with the Operations BB (#202): opt-in, bounded
/metricsoneoapi-stac/eoapi-stac-auth-proxy, aServiceMonitor+ dashboard panels ineoapi-k8s, with EOEPCA enabled via Helm values only. Tracing and per-collection analytics are out of scope.Relates to #202 and developmentseed/eoAPI#193.
🤖 Generated with Claude Code