-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meta monitoring revamp #155
Draft
Imshelledin21
wants to merge
40
commits into
grafana:main
Choose a base branch
from
Imshelledin21:meta-monitoring-revamp
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains 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
- Included Grafana, Mimir and Tempo dashboards. - Updated Loki Dashboards
- Reorganized dashboards by product
Added Mimir and Tempo recording rules
…s, logs, events, traces
Updated values.yaml to enable metric collection of mimir and loki Update metrics-config.yaml to utilize module configmaps
Alloy metrics
Alloy logs
Cleaned up alloy log configs
Alloy metrics config cleanup
`Alloy` section dispersed to each Alloy Deployment.
Major cleanup of the helm chart and configurations.
minor clean up of various items
Update alloy chart version to 0.7.0
Added in alloy-singleton for mimir/loki rules management
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.
Major overhaul of this chart to expand it's capabilities for meta-monitoring Grafana Products.
Alloy deployment split into 4 separate deployments.
The overall configs are relatively simple at this point in time, mostly so I could prove out the concept and have something functioning that could be built upon and further refined.
Alloy Metrics
Can be enabled or disabled
Configurable to enable scraping and remote-writing metrics from the following:
Currently each component is able to scrape metrics from a specified namespace or list of namespaces. Each components discovery/scrape configs are modular, creating a configmap for the component specific configs, and adding a config section to the alloy-metrics configmap, only if that component is enabled.
Alloy Logs
Can be enabled or disabled
Configurable to collect pod logs from a list of specified namespaces.
Alloy Events
Can be enabled or disabled
Configurable to collect kubernetes event logs from a list of specified namespaces
Alloy Traces
Can be enabled or disabled
Will be configured to collect OTEL/Jaeger traces
Next steps for Alloy configs
Next steps for the chart overall
PrometheusRule
kubernetes resources for recording/alert rules for Mimir/Loki with the ability to have alloy load them into the Grafana Cloud or local Mimir and Loki instances.