You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Besides exposing the Prometheus UI/API, it could provide convenience methods to configure scrape targets and rules directly, without requiring users to write and mount a complete prometheus.yml, for example:
very reasonable, configuring these things is a nightmare, see if you can make your changes forwards compatible with a future lgtm container per #733
What do you mean by "forward compatible"? grafana-otel-lgtm seems to be an all-in-one container that includes Prometheus along with several other services.
Activity
alexanderankin commentedon Jul 5, 2026
very reasonable, configuring these things is a nightmare, see if you can make your changes forwards compatible with a future lgtm container per #733
aeroyorch commentedon Jul 5, 2026
What do you mean by "forward compatible"? grafana-otel-lgtm seems to be an all-in-one container that includes Prometheus along with several other services.
alexanderankin commentedon Jul 5, 2026
i mean like put it in a place that would make it obvious that the prometheus and lgtm container belong to one area/together
aeroyorch commentedon Jul 5, 2026
Ah, you mean in terms of an optional dependency group, right? In that case, maybe an
observabilityextra would fit both.alexanderankin commentedon Jul 5, 2026
aeroyorch commentedon Jul 5, 2026
I don't know if I'd lean towards two separate groups, following the existing testcontainers structure:
prometheus:PrometheusContainer(and potentiallyAlertManagerContainerin the future)grafana: Grafana-related componentsThey're different providers, even if they're often used together.