Fix: [BOUNTY $280] Observability — Prometheus + Grafana + Loki + Alerting

[willkhinz]

Fix: [BOUNTY $280] Observability — Prometheus + Grafana + Loki + Alerting

🔍 Analysis

The issue lies in the incomplete configuration of the gitea job in the Prometheus settings, specifically in the scrape_configs section of the prometheus.yml file. The static_configs and targets for the gitea job are missing, preventing Prometheus from scraping metrics from the Gitea service.

🛠️ Implementation

To resolve the issue, the gitea job in the prometheus.yml file needs to be updated with the correct static_configs and targets. The corrected configuration should include the port on which the Gitea service exposes its metrics. Assuming Gitea exposes its metrics on port 3000, the updated configuration would be:

- job_name: gitea
  static_configs:
    - targets: ["gitea:3000"]

This change allows Prometheus to scrape metrics from the Gitea service, enhancing observability.

✅ Verification

To verify the fix, the following steps can be taken:

1. Update the prometheus.yml file with the corrected gitea job configuration.
2. Restart the Prometheus service to apply the changes.
3. Check the Prometheus dashboard to confirm that metrics from the Gitea service are being scraped successfully.
4. Verify that the metrics are being displayed correctly in Grafana and that alerting rules based on these metrics are functioning as expected.
5. Test the Loki logging integration to ensure that logs from the Gitea service are being properly collected and displayed.

Resolves #10

---

Payout Info:

• EVM: 0x78564c4ED88577Cc144e769F86B1a76BDB50B941
• SOL: BzNHSTRuUT4hkbhK7Y9wdp8V6W1iYewSik2VdGGG6pPB
• RTC: RTCff2adc3db75084be4b109aaecab1368f313fd357