Extensions 2.0 Monitoring configurations limit

Roeir5 — Tue, 29 Apr 2025 11:35:46 GMT

Hi everyone,

I’ve built a Python-based custom script extension (v2.0) that runs locally on each OneAgent host (no remote endpoints).
Each endpoint in the extension definition corresponds to a single script executed on the host itself.

Because these scripts are host-specific, we currently create a separate monitoring configuration per host rather than at the Host Group or Environment level. Our Dynatrace Managed cluster now contains roughly 1 000–2 000 hosts (mix of on-prem VMs, EC2 instances, and K8s nodes) that all require this extension.

I’d appreciate clarification on two points:

Configuration-per-extension limit: I’ve read that each extension is capped at 100 monitoring configurations. Is this limit hard-coded, or can it be increased on a Dynatrace Managed deployment?
Scaling strategy: If the limit is fixed and we must create multiple copies of the extension to cover every host: Are there recommended approaches for minimizing operational overhead (e.g., version alignment, automated rollout, naming conventions)? Any lessons learned from maintaining many near-identical extensions?

Thanks in advance for your insights!

- Roei

Re: Extensions 2.0 Monitoring configurations limit

JeanBlanc — Wed, 23 Jul 2025 13:26:48 GMT

Hi 🙂
Same issue and same question here !

Thanks in advance.

topic Extensions 2.0 Monitoring configurations limit in Extensions

Extensions 2.0 Monitoring configurations limit

Re: Extensions 2.0 Monitoring configurations limit