Skip to content
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

Monitoring Dashboard Samples #4

Merged
merged 3 commits into from
Mar 7, 2024

Conversation

bombastictranz
Copy link
Owner

microservices-grpc-monitoring-gce 01
Stock control supervisors

stevezease and others added 3 commits March 5, 2024 21:20
…alerts

Add new recommended alerts for single gce vms
* updated layout for rabbitmq prometheus dashboard

* updated the layout of the rabbitmq dashboard

* took new screenshots for rabbitmq dashboard

* updated dashboard json and screenshot to have sparkline on all scorecard charts
@bombastictranz bombastictranz added bug Something isn't working documentation Improvements or additions to documentation duplicate This issue or pull request already exists enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed invalid This doesn't seem right question Further information is requested wontfix This will not be worked on labels Mar 7, 2024
@bombastictranz bombastictranz self-assigned this Mar 7, 2024
Copy link

codeautopilot bot commented Mar 7, 2024

PR summary

The Pull Request introduces several changes to the monitoring dashboard samples and alert policies for Google Cloud Platform (GCP) resources, specifically for Google Compute Engine (GCE) VM instances and RabbitMQ Prometheus dashboards.

  • New Alert Policies: Four new alert policy templates for GCE VM instances have been added, targeting specific VMs rather than all VMs in a project. These alerts cover high CPU utilization, high disk utilization, memory utilization, and host error logs within individual VM instances.
  • Metadata Updates: The metadata.yaml file has been updated to include descriptions and versioning for the new alert policies.
  • RabbitMQ Dashboard Updates: The RabbitMQ Prometheus dashboard JSON configuration has been significantly updated. Changes include layout adjustments, the addition of sparkline charts to scorecards, and the restructuring of widgets to provide a more detailed and organized view of RabbitMQ metrics.
  • RabbitMQ Dashboard Images: Images of the RabbitMQ dashboard have been updated, and some have been removed, likely to reflect the new layout and configuration changes.

Suggestion

  • Review Alert Thresholds: Ensure that the thresholds for the new alert policies are appropriate for the expected workload and performance characteristics of the VM instances.
  • Test Alert Policies: Before deploying the new alert policies, they should be tested to ensure they trigger as expected and do not produce false positives or negatives.
  • Validate Dashboard Changes: The RabbitMQ dashboard changes should be reviewed by a RabbitMQ expert to ensure that the new layout and metrics presented are useful and accurately represent the health and performance of RabbitMQ instances.
  • Update Documentation: Accompanying documentation should be updated to reflect the new alert policies and dashboard changes, providing users with guidance on how to use and interpret them.

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 16.19%

Have feedback or need help?
Discord
Documentation
support@codeautopilot.com

@bombastictranz bombastictranz merged commit 0214a98 into bombastictranz:patch-1 Mar 7, 2024
6 checks passed
bombastictranz pushed a commit that referenced this pull request Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation duplicate This issue or pull request already exists enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed invalid This doesn't seem right question Further information is requested wontfix This will not be worked on
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants