OneAgent and ActiveGate version 1.299 are the last versions supporting OneAgent and ActiveGate Extensions 1.0 framework. You can continue using Extensions 1.0 if you stay at OneAgent or ActiveGate version 1.299. Note that this means you'll be using an unsupported Python version 3.8. We strongly recommend migrating your extensions to the latest Extensions 2.0 framework.
For more information, see General guidance and how to migrate.
Learn about the limitations and requirements of ActiveGate extensions.
ActiveGate extensions are executed by an Environment ActiveGate. Note that you can't execute ActiveGate extensions using an Environment ActiveGate that's configured for multi-environment support.
The ActiveGate extension module limits the amount of data sent to Dynatrace Server.
The data is trimmed after reaching the limit, but all the data up to the limit is still sent. For some entities, the plugin module raises an exception when the limit is reached. The exception is displayed in Settings > Monitoring > Monitored technologies for a related extension.
The table below presents the entities where limits apply, along with the maximum values.
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.
All extensions are written in Python. Because of how Python works, there may be ambiguities when Python uses import
statements. Namely, if there are multiple extensions using files that are identically named, there may be issues importing those files. Because of this, you should use unique file names that are unlikely to appear in other extensions. For example, instead of a generic file name like utils.py
, use something like my_extension_utils.py
.