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.
One of the key features of Dynatrace is its ability to detect and analyze performance issues before your customers are affected by them. This is achieved by a system of smart alerting, which allows you to find the root cause of performance issues even in complex environments. In order to take advantage of this functionality, your extension may specify alerts, which will be generated when unexpected behavior is detected within monitored processes.
For any timeseries reported by your extension, it's possible to define criteria for multiple alert types. To do this, the alert_settings section must be added to your extension metrics definition. Provided below is a sample plugin.json definition. Please note, that no changes in the extension code itself are required.
{"metrics": ["key": "counter","alert_settings": [{"alert_id": "counter_alert_high","event_type": "PGI_CUSTOM_PERFORMANCE","event_name": "Enormous counter rate","threshold": 10.0,"alert_condition": "ABOVE","samples": 5,"violating_samples": 3,"dealerting_samples": 5},{"alert_id": "counter_alert_low","event_type": "PGI_CUSTOM_ERROR","event_name": "Low counter rate","threshold": 1.0,"alert_condition": "BELOW","samples": 5,"violating_samples": 5,"dealerting_samples": 3}]]}
Please refer to plugin.json reference to find details about configuring alerts.
Once the definition is provided, the alert activation, as well as deactivation, is automatically handled by Dynatrace Cluster Node. When an alert is displayed, you'll see detailed information about the problem and affected components on the corresponding Problem page.