Extend the platform, empower your team.
2.0 remote extension that collects data from the InterSystems IRIS APIs.
Gain insights into the performance of your InterSystems IRIS instances. View metrics and events in context with your OneAgent collected data in the Dynatrace UI. Make use of powerful charting and dashboarding features. Allow the Davis® AI causation engine to generate baselines and alert you when anomalies are detected in designated metrics.
Connects to and collects data from the InterSystems IRIS REST API.
An InterSystems IRIS overview dashboard is included with the extension. This includes links to access the IRIS instance entities detected.
Metrics are associated with different feature sets that can be enabled or disabled as needed. Metrics will be collected once per minute.
Cannot be disabled.
Number of currently active web session IDs on this server
Note: this feature set will also cause alerts on the alerts API endpoint to be reported in Dynatrace as log events.
Size of database buffers the write daemon wrote during its most recent cycle
Amount of time the write daemon spent writing buffers to databases during its most recent cycle
The list of 'known' or 'documented' metrics in IRIS is available in the InterSystems documentation. It is possible that there will be additional metrics on the Prometheus style page that we collect these metrics from.
If you enable this feature set, these undocumented metrics will be collected and reported but without any metadata (e.g. display name and unit). They will still be available for charting and alerting as needed. If you would like to configure metadata for these you can do so by editing them in the Metrics page.
A database may enter a corrupted state if it attempts to expand beyond it's maximum size. A log event with the title "Database <database> will be unable to expand!" will be reported if we detect the difference between the current size and the maximum size is less than the expansion size of the database.
If there is an error when collecting the metrics/events a log event/record will be reporting and visible on the IRIS instance entity with details on the error.
If you have the 'system-alerts' feature set enabled, the alerts API endpoint will be polled and the alerts reported in Dynatrace as log events.
Find 'InterSystems IRIS' in the in-product Extensions or Hub page and activate (if offline you can download the extension from this Hub page in the 'Versions' section and install as a custom extension).
Once activated in your environment you can create monitoring configurations. Each monitoring configuration can have up to 100 IRIS instances configured.
First select the desired ActiveGate group that will run the monitoring configuration.
For each cluster configure a IRIS Instance Endpoint:
At the monitoring configuration level the following configurations will apply to all endpoints:
The Log level will be set at the monitoring configuration level and will apply to all endpoints. INFO by default. DEBUG logging is only needed when investigating issues with support.
Finally, enable the desired feature sets (refer to the Details tab for what metrics are associated with which feature sets).
If the 'undocumented-metrics' feature set is enabled, the extension will collect custom and any undocumented IRIS metrics available on the metrics API page. As these metrics are unknown in advance they will be missing metadata such as a display name, description, and unit. They will be usable as-is but if you'd like you can configure metadate for these yourself.
Refer to the Metrics browser documentation page for details on how to do this.
There is no charge for obtaining the extension, only for the data (metrics & events) that the extension ingests. The details of license consumption will depend on which licensing model you are using. This will either be Dynatrace classic licensing or the Dynatrace Platform Subscription (DPS) model.
License consumption is based on the number of metric data points ingested. The following formula will provide approximate annual data points ingested assuming all feature sets are enabled:
(64 + (1 x processTypes) + (5 x ipAddress:port) + (7 x databases) + (2 x journalTypes) + (3 x smhPurpose) + (7 x namespaces) + (6 x wqmCategories)) x 60 min x 24 h x 365 days data points/year
In the classic licensing model, metric ingestion will consume Davis Data Units (DDUs) at the rate of .001 DDUs per metric data point.
Multiply the above formula for annual data points by .001 to estimate annual DDU usage.
This extension will report log events in 2 situations:
License consumption is based on the size (in bytes) of data ingested & processed, retained, and queried so there is not a single formula to estimate the total consumption from this extension. Consult the log management and analytics documentation for details on the other dimensions that will effect license consumption.
In the classic licensing model, log record ingestion will consume Davis Data Units (DDUs) at the rate of 100 DDUs per Gigabyte of log records ingested.
In log monitoring classic, license consumption is based on the number of ingested log records.
In the classic licensing model, log record ingestion will consume Davis Data Units (DDUs) at the rate of .0005 DDUs per ingested log record.
Multiply estimated ingested log records by .0005 to estimate DDU usage from log records.
Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual metrics can be activated and deactivated by your administrator during configuration.
No release notes