Skip to content

Request to add Prometheus and Grafana as first-class commodities in common-dev-env #183

@cmbaike

Description

@cmbaike

Context / Background

As more services adopt observability standards (e.g., exposing /metrics or /actuator/prometheus endpoints), developers need a consistent way to inspect runtime behaviour locally - including request rates, JVM metrics, error patterns, and custom business metrics.

Today, observability setup is fragmented or ad-hoc across services, which leads to:

  • Inconsistent local debugging workflows

  • Duplicate or bespoke monitoring setups per repo

  • Difficulty validating metrics before deploying to shared environments

  • Lack of a standard place to view dashboards during development

Introducing Prometheus and Grafana as shared commodities in the dev environment establishes a single, predictable observability stack that mirrors how services are monitored in higher environments, while remaining decoupled from any specific application.

I’ve implemented and tested this setup in my local development environment to validate that Prometheus scrapes metrics correctly and Grafana provisioning works as expected with the proposed mounts and structure.

If there are no objections to the approach, I’m happy to raise a PR with the changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions