Grafana "Anticapture V2" data visualization Dashboard#1834
Grafana "Anticapture V2" data visualization Dashboard#1834PedroBinotto merged 23 commits intodevfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
|
🚅 Deployed to the anticapture-pr-1834 environment in anticapture-infra
16 services not affected by this PR
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fc7d5f82a4
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
…nticapture into fix/prometheus-indexer-alerts
This reverts commit f4f9b61.
Fix: prometheus indexer alert spam
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5bf6da0146
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2f9d7cc33b
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| const meter = meterProvider.getMeter("anticapture-gateway"); | ||
|
|
||
| export const httpRequestDuration = meter.createHistogram( | ||
| "http_server_request_duration_seconds", |
There was a problem hiding this comment.
Use a distinct metric name for gateway request latency
This introduces a new histogram named http_server_request_duration_seconds for anticapture-gateway, which is the same series family already used by DAO APIs. Our alert rules (infra/monitoring/alerts.yml, HighLatency and HighErrorRate) aggregate http_server_request_duration_seconds_* without a job filter, so gateway traffic is now mixed into API SLO signals; in practice, high-volume low-error gateway traffic can mask API regressions (or vice versa), causing missed or misleading alerts. Prefer a gateway-specific metric name (or update alerts to scope by job) so API alert semantics stay stable.
Useful? React with 👍 / 👎.
What
Adds an observability layer and a new Grafana dashboard ("Anticapture V2") for monitoring the platform's request traffic, cache behaviour, and system health.
Changes
apps/api-gatewayhttp_server_request_duration_seconds(histogram) per request, labelled by method, route, status code, andclient_source(derived from thex-client-sourcerequest header).apps/gatefulcache_requests_total(counter) per cache lookup, labelled byresult(hit,miss,corrupt) androute.apps/dashboardx-client-sourceheader through the Next.js proxy so the gateway can attribute traffic to the frontend.packages/anticapture-clientx-client-source: anticapture-frontendon every outgoing API request.infra/monitoring/grafana/dashboards/anticapture-v2.jsonNew dashboard with the following sections: