Merged
Conversation
This change introduces a programmatic approach to managing dashboards, recording rules, and alerting rules for the activity system. This approach utilizes Jsonnet and Grafonnet to define observability configurations. These configurations are generated into a kustomize component that can be included in the system's deployment to install the observability tools into the environment.
scotwells
requested review from
JoseSzycho,
OscarLlamas6,
cc-datum,
drewr,
ecv and
zachsmith1
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.
Summary
This change introduces a programmatic approach to managing dashboards, recording rules, and alerting rules for the activity system. This approach utilizes Jsonnet and Grafonnet to define observability configurations.
These configurations are generated into a kustomize component that can be included in the system's deployment to install the observability tools into the environment.
Dashboards
This PR introduces 2 dashboards that can be used to understand the performance and current health of the activity system.
Audit Log Pipeline
The audit log pipeline dashboard covers the audit log pipeline components so we understand the number of audit logs being generated by apiservers, how quickly they're being processed by Vector and NATS, write performance into Clickhouse, and errors within the pipeline. It also contains high-level metrics around activity api requests for quick at-a-glance context on the overall pipeline.
Activity API Overview
The activity api overview dashboard focuses more on end-user interactions with the activity system to understand querying performance or errors encountered by end-users. It also provides a quick glance into clickhouse performance to determine whether clickhouse query performance is responsible for end-user issues.
Resources
Relates to datum-cloud/enhancements#536