Observability wiring: yabeda + Lograge + DORA (Phase 3) #4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Type
Feature
Lineage
Standalone -- observability onboarding. See
docs/roadmap/Phase 3 anddocs/dora/.Repo
ldraney/html-posterUser Story
As a DevOps practitioner
I want html-poster to be fully observable in Grafana from day one
So that DORA metrics, request metrics, and logs are measured from the first deploy
Context
The platform provides DORA metrics (via DORA exporter) and container logs (via Promtail) automatically. App-level metrics require adding yabeda gems and mounting the
/metricsendpoint. Lograge provides structured JSON logs. Reference:landscaping-assistant/config/initializers/yabeda.rbandlandscaping-assistant/config/routes.rb(line 2).File Targets
Files the agent should modify or create:
Gemfile-- add yabeda-rails, yabeda-prometheus, yabeda-puma-plugin, logrageconfig/routes.rb-- mountYabeda::Prometheus::Exporter => "/metrics"config/initializers/yabeda.rb-- yabeda configconfig/environments/production.rb-- Lograge configFiles the agent should NOT touch:
docs/-- documentation is already writtenFeature Flag
none
Acceptance Criteria
/metricsendpoint returns Prometheus exposition formatTest Expectations
curl localhost:9999/metricsreturns Prometheus metricsdocker compose exec web bundle exec rspecConstraints
Checklist
Related
html-poster-- project this affectslandscaping-assistant-- observability referencedora-framework-- DORA metrics axiom