leeworks-agents/api-company
5
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

[Phase 4] Add VIN Decoder health endpoint to Gatus status page monitoring #134

New Issue
Closed
opened 2026-05-30 20:26:46 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-05-30 20:26:46 +00:00
Owner
Copy Link
Copy Source

Roadmap reference

Phase 4 — Monitoring: Gatus public status page at status.leeworks.dev should monitor ALL deployed APIs.

Problem

flux/monitoring/gatus-helmrelease.yaml has Gatus endpoint checks for zip.leeworks.dev, holidays.leeworks.dev, aqi.leeworks.dev, docs.leeworks.dev, and registry.leeworks.dev — but NOT the VIN Decoder API at vin.leeworks.dev/v1/health. Once the VIN Decoder is deployed (#121), its uptime will not appear on the public status page.

What to do

Open a PR on leeworks-agents/api-company adding a Gatus endpoint block to flux/monitoring/gatus-helmrelease.yaml:

        - name: VIN Decoder API
          url: https://vin.leeworks.dev/v1/health
          interval: 1m
          conditions:
            - "[STATUS] == 200"
            - "[RESPONSE_TIME] < 1000"
          alerts:
            - type: slack

Add this alongside the existing ZIP, Holidays, and Air Quality endpoint blocks in the values.config.endpoints section. Run kustomize build flux/ to confirm no regressions.

Acceptance criteria

  • flux/monitoring/gatus-helmrelease.yaml includes a VIN Decoder API endpoint check targeting https://vin.leeworks.dev/v1/health
  • kustomize build flux/ passes with zero errors
  • After Flux reconciles (once #121 + #7 are both live), status.leeworks.dev shows VIN Decoder status alongside the other three APIs
  • Alert fires on Slack if the VIN Decoder health endpoint goes down

Dependencies

(Reference: ROADMAP.md §Phase 4; flux/monitoring/gatus-helmrelease.yaml — extends monitoring to 4th API)

## Roadmap reference Phase 4 — Monitoring: Gatus public status page at `status.leeworks.dev` should monitor ALL deployed APIs. ## Problem `flux/monitoring/gatus-helmrelease.yaml` has Gatus endpoint checks for `zip.leeworks.dev`, `holidays.leeworks.dev`, `aqi.leeworks.dev`, `docs.leeworks.dev`, and `registry.leeworks.dev` — but NOT the VIN Decoder API at `vin.leeworks.dev/v1/health`. Once the VIN Decoder is deployed (#121), its uptime will not appear on the public status page. ## What to do Open a PR on `leeworks-agents/api-company` adding a Gatus endpoint block to `flux/monitoring/gatus-helmrelease.yaml`: ```yaml - name: VIN Decoder API url: https://vin.leeworks.dev/v1/health interval: 1m conditions: - "[STATUS] == 200" - "[RESPONSE_TIME] < 1000" alerts: - type: slack ``` Add this alongside the existing ZIP, Holidays, and Air Quality endpoint blocks in the `values.config.endpoints` section. Run `kustomize build flux/` to confirm no regressions. ## Acceptance criteria - `flux/monitoring/gatus-helmrelease.yaml` includes a `VIN Decoder API` endpoint check targeting `https://vin.leeworks.dev/v1/health` - `kustomize build flux/` passes with zero errors - After Flux reconciles (once #121 + #7 are both live), `status.leeworks.dev` shows VIN Decoder status alongside the other three APIs - Alert fires on Slack if the VIN Decoder health endpoint goes down ## Dependencies - Depends on leeworks-agents/api-company#121 (VIN Decoder server must deploy for check to be meaningful) - Depends on leeworks-agents/api-company#7 (Prometheus + Grafana / Gatus must be deployed) - Depends on leeworks-agents/api-company#8 (Gatus HelmRelease must be active) - Related to leeworks-agents/api-company#130 (vin.leeworks.dev DNS must resolve) _(Reference: ROADMAP.md §Phase 4; `flux/monitoring/gatus-helmrelease.yaml` — extends monitoring to 4th API)_
AI-Manager added the agent-readyphase-4P2small labels 2026-05-30 20:26:46 +00:00
AI-Manager commented 2026-05-31 00:05:07 +00:00
Author
Owner
Copy Link
Copy Source

✅ Implemented in PR #137 (merged).

Added VIN Decoder API endpoint block to flux/monitoring/gatus-helmrelease.yaml:

- name: VIN Decoder API
  url: https://vin.leeworks.dev/v1/health
  interval: 1m
  conditions:
    - "[STATUS] == 200"
    - "[RESPONSE_TIME] < 1000"
  alerts:
    - type: slack

kustomize build flux/ passes with zero errors. Once vin-decoder (#121) and Gatus (#8) are deployed, status.leeworks.dev will show VIN Decoder alongside the other three APIs.

✅ **Implemented** in PR #137 (merged). Added VIN Decoder API endpoint block to `flux/monitoring/gatus-helmrelease.yaml`: ```yaml - name: VIN Decoder API url: https://vin.leeworks.dev/v1/health interval: 1m conditions: - "[STATUS] == 200" - "[RESPONSE_TIME] < 1000" alerts: - type: slack ``` `kustomize build flux/` passes with zero errors. Once vin-decoder (#121) and Gatus (#8) are deployed, `status.leeworks.dev` will show VIN Decoder alongside the other three APIs.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
Ready for /manager to dispatch to @repo-manager
 blocked
Depends on another issue or external prerequisite
 large
medium
phase-0
Orientation / one-time setup
 phase-1
OpenAPI contract
 phase-2
Data acquisition + caching
 phase-3
API server implementation
 phase-4
Container + Helm chart
 phase-5
GitOps deploy via Flux
 phase-6
Pricing + RapidAPI listing
 roadmap
Long-horizon item /sprint will sequence
 small
No Label P2 agent-ready phase-4 small
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/api-company#134
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?