Learn about the limitations and requirements of ActiveGate plugins.
Supported ActiveGate types
ActiveGate plugins are executed by an Environment ActiveGate. Note that you can't execute ActiveGate plugins using an Environment ActiveGate that's configured for multi-environment support.
The ActiveGate plugin module limits the amount of data sent to Dynatrace Server. The table below presents the entities where limits apply, along with the maximum values.
|Groups||Number of device groups created per minute||50|
|Devices||Number of devices created per minute||500|
|Measurements limit||Number of metrics including dimensions per minute||100,000|
|Events limit||Number of events per minute||100|
|Event title length||Length of event title string||1,024|
|Event description length||Length of event description string||10,240|
|Event properties limit||Number of elements in event properties dictionary||100|
|Event property key length||Length of event property key string||100|
|Event property value length||Length of event property value string||4,000|
Filtering metrics, problems, and events
Remember there are several filtering systems. Custom metrics and events are limited by quotas. If ActiveGate module quotas are in use, you'll find this information in the Remote Plugin Module logs.
Naming Python plugin files
All plugins are written in Python. Because of how Python works, there may be ambiguities when Python uses
import statements. Namely, if there are multiple plugins using files that are identically named, there may be issues importing those files. Because of this it's advised that you use unique file names that are unlikely to appear in other plugins. So, for example, instead of generic file names like
utils.py, use something unique, for example