New Container: Prometheus

[aeroyorch]

Feature Request: PrometheusContainer

What is the new container you'd like to have?

I'd like to propose a PrometheusContainer for integration testing with Prometheus.

Relevant resources:

• Docker image: https://hub.docker.com/r/prom/prometheus
• Prometheus docs: https://prometheus.io/docs/introduction/overview/

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:

prometheus = (
    PrometheusContainer()
    .with_scrape_target("app", app_container, port=8080, metrics_path="/metrics")
    .with_scrape_target("redis", redis_exporter)
)

The container could generate the corresponding prometheus.yml internally while still allowing users to provide a custom configuration file if needed.

Why not just use a generic container for this?

While DockerContainer("prom/prometheus") works, most tests usually need additional setup:

• Configuring scrape targets.
• Providing a Prometheus configuration.
• Waiting until Prometheus is ready to accept requests.
• Reload Prometheus on config change.
• etc.

Other references

A similar idea has already been discussed in the testcontainers-java

[alexanderankin]

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]

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.

[alexanderankin]

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]

Ah, you mean in terms of an optional dependency group, right? In that case, maybe an observability extra would fit both.

[alexanderankin]

Yes something like that

…

On Sun, Jul 5, 2026, 11:13 AM Jorge Rocamora ***@***.***> wrote: *aeroyorch* left a comment (testcontainers/testcontainers-python#1075) <#1075 (comment)> Ah, you mean in terms of an optional dependency group, right? In that case, maybe an observability extra would fit both. — Reply to this email directly, view it on GitHub <#1075?email_source=notifications&email_token=ACECGJCKM4U4FJATYURTRVL5DJWCFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBYGY2TCNZTHEY2M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4886517391>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACECGJEZC32NHWJV5S6KYGL5DJWCFAVCNFSNUABEKJSXA33TNF2G64TZHM4DKOBQGI4DCOJ3JFZXG5LFHM2DQMJSGU4TENBZGGQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ACECGJGUBGMY2C6PIWS4KLT5DJWCFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBYGY2TCNZTHEY2M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ACECGJHR6Q5YIJAB2NPKZUL5DJWCFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBYGY2TCNZTHEY2M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

[aeroyorch]

I don't know if I'd lean towards two separate groups, following the existing testcontainers structure:

• prometheus: PrometheusContainer (and potentially AlertManagerContainer in the future)
• grafana: Grafana-related components

They're different providers, even if they're often used together.