Skip to content

Add production whitelabel LB request dashboard with daily averages - #19

Open
akshay-ghl wants to merge 1 commit into
recover/sep18-custom43-integratedfrom
ai/production-whitelabel-lb-dashboard
Open

akshay-ghl wants to merge 1 commit into
recover/sep18-custom43-integratedfrom
ai/production-whitelabel-lb-dashboard

Conversation

@akshay-ghl

@akshay-ghl akshay-ghl commented Nov 11, 2026 •

Copy link
Copy Markdown

Adds a production dashboard export for completed HTTP requests through the whitelabel LB at 35.202.49.152, including customer domains. It uses the companion proxy instrumentation and a separate Service activation change; no HyperDX application release or new collector is required.

The 12 panels provide selected-range totals, average requests/day, average RPS, request-rate/status graphs, host-filtered totals and rates, overflow volume, enabled targets and exporter errors. Daily averages divide by the exact selected duration in days (10 days → divide by 10; 12 hours → divide by 0.5). Host filtering affects only explicitly named selected-host panels; all-host totals retain every counted domain, including overflow.

Named-host counts may be partial after the per-pod 1,000-host cap. The dashboard describes this limitation and excludes any billing/exact-count claim. Missing telemetry is not coerced to zero; there is no historical backfill.

Dependencies

  1. Proxy instrumentation: https://github.com/GoHighLevel/highlevel-infrastructure/pull/1293
  2. Service activation after listener rollout: https://github.com/GoHighLevel/highlevel-infrastructure/pull/1294

Validation

Current remote gate: Code Quality Gates is blocked by hardcoded_api_keys (critical), while Orca Secrets passed and SonarQube remains queued. Details: https://devtools.msgsndr.net/quality-gates/hyperdx/19. Per the user's existing instruction, these findings are left for the gate owner; no credential cleanup or gate bypass is included. Local validation below is separate from remote gate status.

  • Exact target branch's DashboardTemplateSchema accepted all 12 tiles.
  • Actual selected-range macro expansion passed for 10 days, 1 day and 12 hours.
  • The existing live proxy scrape job retains the new metric names and host label; actual ingestion of the new counters remains a post-release check.
  • Digest-pinned Prometheus 3.5.0 parsed all 11 expressions and passed reset-aware, multi-replica totals, daily averages, status/host selection, overflow and missing-data tests.
  • Staged-file lint/formatting, git diff --check, and ai-setup check-project passed. No application code changed; full application suites were not run.
  • Global Git hooks are active in this workspace; the repository's staged-file checks were also run manually because the global hooks path takes precedence over .husky.

Targets the custom production branch, which already has selected-range macros and visible Min/Max/Last legends (PR #12). Not imported or deployed. Live rendering/screenshots, variables against production telemetry, ten-day production query capacity and count reconciliation remain acceptance checks after the companion changes are released. See dashboard-exports/prd/WHITELABEL-LB-REQUESTS.md.

@orca-security-us orca-security-us Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Orca Security Scan Summary

Status Check Issues by priority
Passed Passed Secrets high 0   medium 0   low 0   info 0 View in Orca

@code-quality-gates

Copy link
Copy Markdown

⛔ This PR is blocked

1 critical check(s) failed. Critical gates enforce security & compliance — the PR cannot merge until they pass. Each failing gate and how to fix it is listed below.


Quality Gate Results

⛔ 1 Critical failed — blocking
⚠️ 2 Warning(s) — non-blocking, please review
✅ 4 Passed

❌ Must fix before merging

hardcoded_api_keys (repo-wide check — may flag existing code outside your changes)

  • docker/otel-collector/custom.config.yaml:55 — Found potential Hardcoded auth/access token
  • packages/api/openapi.json:5006 — Found potential Slack Webhook URL
  • packages/api/openapi.json:5232 — Found potential Slack Webhook URL
  • packages/api/src/routers/api/__tests__/webhooks.int.test.ts:13 — Found potential Slack Webhook URL
  • packages/api/src/routers/api/__tests__/webhooks.int.test.ts:636 — Found potential Slack Webhook URL
  • …and 22 more (see detailed results)
  • ✅ How to fix: Remove this key and replace it with a reference from the secrets manager.
  • 📖 Full docs & exception process

⚠️ Warnings (non-blocking — worth reviewing)

  • block_clickhouse_client_create_client_usage (8 items) — detailed results (inline comments only on changed lines) · 📖 docs
  • dependency_license_check (1 item) — detailed results (inline comments only on changed lines) · 📖 docs

🔍 View detailed quality gate results

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant