IBM Informix extension
- Latest Dynatrace
- Extension
Remotely monitor your IBM Informix instances
Get started
Overview
Remotely monitor IBM Informix databases where OneAgent installation isn't possible.
Use cases
- Monitor health and state of Informix instances.
- Detect and alert on anomalous behavior.
- Understand the resource impact that your applications have on your database.
- Understand the impact of resource shortages, locks or other database issues have on your application by observing the database server itself.
Requirements
- IBM Informix JDBC driver must be present on the ActiveGate(s) in one of the below directories:
- Windows:
C:\ProgramData\dynatrace\remotepluginmodule\agent\conf\userdata\libs - Linux:
/var/lib/dynatrace/remotepluginmodule/agent/conf/userdata/libs/
- Windows:
Compatibility information
- Informix v. 14.10+
- Informix Driver v. 4.5.x+
Permissions
In order to properly execute the SQL queries, the user account utilized by the extension must have read access to the sysmaster database and the below tables:
syslockssyssessionssysdatabasessysprofilesysseglstsysvpprofsysdbspacessyschunkssysshmvalssyschktabsysdbstabsysptprofsystabinfo
Activation and setup
- Find the extension in Dynatrace Hub and add it to your environment.
- Add a monitoring configuration for every IBM Informix instance you'd like to monitor.
Details
This extension collects performance metrics through various SQL queries executed on the Informix instance.
Licensing and costs
There is no charge to use the extension. You are only charged for the data that the extension ingests.
The IBM Informix extension ingests custom metrics, which consume Davis Data Units (DDUs) (Dynatrace classic license) or Metrics powered by Grail (DPS), according to your license model.
To estimate the number of metric data points produced by the extension per minute, use the following formula:
(15 * # of instances) + (2 * # of databases) + (2 * # of tables) + (5 * # of dbspaces)
Dynatrace Platform Subscription
In the Dynatrace Platform Subscription, metric ingestion consumes Metrics powered by Grail according to the number of ingested metric data points.
To calculate the approximate yearly consumption, apply the following calculation: <metric data points per minute> * 60 minutes * 24 hours * 365 days.
Dynatrace classic license
In the classic licensing model, metric ingestion consumes 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.
The DDU cost above does not include any possible log events or custom events that are triggered by the extension. For more information, see DDU events.
Feature sets
When activating your extension using a monitoring configuration, you can limit monitoring to one of the feature sets. To work properly, the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
overflow
| Metric name | Metric key | Description |
|---|---|---|
| Overflow - User | informix.instance.ovuser | Number of times a new session was attempted to exceed the maximum number of sessions |
| Overflow - Lock | informix.instance.ovlock | Number of times that sessions attempted to exceed the maximum number of locks |
| Overflow - Transaction | informix.instance.ovtrans | Number of times that a thread attempted to exceed the maximum number of transactions |
locks
| Metric name | Metric key | Description |
|---|---|---|
| Lock waits | informix.instance.lockwts | Number of times that a session had to wait for a lock |
| Locks - Database | informix.database.locks | Number of locks on the database |
dbspace
| Metric name | Metric key | Description |
|---|---|---|
| Database Space Percent Free | informix.dbspace.percent_free | The percent of the dbspace that is free |
| Chunk - Reads | informix.dbspace.chunks_read | Number of times a read operation has been performed on the database's chunks |
| Chunk - Writes | informix.dbspace.chunks_written | Number of times a write operation has been performed on the database's chunks |
| Chunk - Pages Read | informix.dbspace.chunk_pages_read | Number of times a read operation has been performed on a page within the database's chunks |
| Chunk - Pages Written | informix.dbspace.chunk_pages_written | Number of times a write operation has been performed on a page within the database's chunks |
default
| Metric name | Metric key | Description |
|---|---|---|
| Shared Memory Segments | informix.instance.count_segments | The count of segments present in the Informix server's shared memory |
| Shared Memory Segment Size | informix.instance.segment_size | The total size of the segment in the Informix server's shared memory |
| Shared Memory Segment Blocks Used | informix.instance.segment_blocks_used | The total number of blocks (4KB of shared memory) used by the segment in the Informix server's shared memory |
| Shared Memory Segment Blocks Free | informix.instance.segment_blocks_free | The total number of blocks (4KB of share memory) used by the segment in the Informix server's shared memory' |
| CPU User Time Count | informix.instance.cpu_user.count | Number of microseconds of user time used each minute |
| CPU System Time Count | informix.instance.cpu_system.count | Number of microseconds of user time used each minute |
buffer-cache
| Metric name | Metric key | Description |
|---|---|---|
| Buffer Cache Hit Ratio - Read | informix.instance.buffer_cache_hit_ratio_read | The ratio of pages read from the memory buffer |
| Buffer Cache Hit Ratio - Write | informix.instance.buffer_cache_hit_ratio_write | The ratio of pages written to the memory buffer |
sessions
| Metric name | Metric key | Description |
|---|---|---|
| Sessions | informix.database.sessions | The number of sessions on the database |
checkpoints
| Metric name | Metric key | Description |
|---|---|---|
| Checkpoint Count | informix.instance.checkpoint.count | The number of checkpoints performed in the last minute |
lru
| Metric name | Metric key | Description |
|---|---|---|
| Least-Recently Used Writes | informix.instance.lruwrites | Number of times that an LRU write was performed |
sequential-scans
| Metric name | Metric key | Description |
|---|---|---|
| Sequential Scan Count | informix.instance.scan.count | Sequential scans performed in the last minute |
tables
| Metric name | Metric key | Description |
|---|---|---|
| Table Pages Used | informix.database.table_pages_used | The number of pages used by a table within the database |
| Table Pages Allocated | informix.database.table_pages_allocated | The number of pages allocated by a table within the database |
| Table Pages Usage | informix.database.table_pages_usage | The percent of pages used by a table within the database |
| Table Data Pages | informix.database.table_data_pages | The number of pages that store data by a table within the database |
| Table Scans | informix.database.table_scans | The number of scans performed on a table within the database |
latest-checkpoint
| Metric name | Metric key | Description |
|---|
