Closed subhrashisdas closed 2 days ago
The changes involve the deletion of several configuration files related to observability tools in a Docker setup. The removed files include configurations for Docker Compose, Grafana dashboards, data sources, and Prometheus settings, as well as a local Tempo configuration. These deletions indicate a significant alteration in the observability setup, potentially simplifying or changing the approach to monitoring and logging within the application.
File Path | Change Summary |
---|---|
utils/observability/docker-compose.yml |
Deleted configuration for Docker Compose, including services for Tempo, Prometheus, and Grafana. |
utils/observability/docker/grafana/provisioning/dashboards/dashboard.yml |
Deleted Grafana dashboard provisioning configuration. |
utils/observability/docker/grafana/provisioning/dashboards/logs_traces_metrics.json |
Deleted Grafana dashboard for visualizing logs, traces, and metrics. |
utils/observability/docker/grafana/provisioning/dashboards/redis_dashboard.json |
Deleted Grafana dashboard specifically for monitoring Redis operations. |
utils/observability/docker/grafana/provisioning/datasources/datasource.yml |
Deleted configuration for data sources (Prometheus, Tempo, Loki) in Grafana. |
utils/observability/docker/prometheus/prometheus.yml |
Deleted configuration settings for Prometheus monitoring. |
utils/observability/docker/tempo/tempo-local.yaml |
Deleted configuration for local Tempo instance setup. |
skip-changelog
, ok-to-test
๐ In the land of code where changes flow,
Configs were deleted, and off they go!
With observability tools now out of sight,
A simpler path may soon feel just right.
Farewell to the dashboards and YAMLs galore,
New adventures await, letโs code even more! ๐
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Description
Cleanup of Monitoring will be done in multiple phases to avoid any disruptions. The first PR is to remove the default monitoring Compose files.
Fixes #
Issue Number
or
Fixes
Issue URL
Automation
/ok-to-test tags="@tag.Sanity"
:mag: Cypress test results
Communication
Should the DevRel and Marketing teams inform users about this change?
Summary by CodeRabbit