Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal] Semantic Conventions for IBM Informix DB (Settings Metrics) #1967

Open
debnathbikram opened this issue Mar 6, 2025 · 0 comments
Labels
enhancement New feature or request experts needed This issue or pull request is outside an area where general approvers feel they can approve triage:needs-triage

Comments

@debnathbikram
Copy link

Propose new conventions

Proposal:

Introduce New Semantic Conventions for Informix Database (Server Side) in OpenTelemetry

Summary

This proposal introduces semantic conventions for monitoring IBM Informix Database within the OpenTelemetry project.
Informix is a widely used database system known for its efficiency in OLTP (Online Transaction Processing) and time-series data handling. Currently, OpenTelemetry lacks specific semantic attributes for Informix. This proposal aims to standardize the metrics for Informix to ensure better observability, performance monitoring, and interoperability across telemetry data sources.

Proposed Semantic Conventions (Specific to Informix DB)

Settings Metrics

    1. Log Enabled
    2. Buffer Log Enabled
    3. Ansi Compliant
    4. NLS Enabled Scan Count
    5. Case Insensitive

Settings Metrics

Metric: db.database.log.enabled

This metric is optional.

Name Instrument Type Units (UCUM) Description
db.database.log.enabled Gauge by Database logging is enabled or not. 1 (Active), 0 (Inactive).
Attribute Type Description Example Requirement Level
database_name String Database name identifier. prod_db; sysmaster Required

Metric: db.database.buff.log.enabled

This metric is optional.

Name Instrument Type Units (UCUM) Description
db.database.buff.log.enabled Gauge by Database Buffered logging is enabled or not. 1 (Active), 0 (Inactive).
Attribute Type Description Example Requirement Level
database_name String Database name identifier. prod_db; sysmaster Required

Metric: db.database.ansi.compliant

This metric is optional.

Name Instrument Type Units (UCUM) Description
db.database.ansi.compliant Gauge by Database is ANSI/ISO-compliant or not. 1 (Active), 0 (Inactive).
Attribute Type Description Example Requirement Level
database_name String Database name identifier. prod_db; sysmaster Required

Metric: db.database.nls.enabled

This metric is optional.

Name Instrument Type Units (UCUM) Description
db.database.nls.enabled Gauge by Database is GLS-enabled or not. 1 (Active), 0 (Inactive).
Attribute Type Description Example Requirement Level
database_name String Database name identifier. prod_db; sysmaster Required

Metric: db.database.case.insensitive

This metric is optional.

Name Instrument Type Units (UCUM) Description
db.database.case.insensitive Gauge by Database is case-insensitive for NCHAR and NVARCHAR columns or not. 1 (Active), 0 (Inactive).
Attribute Type Description Example Requirement Level
database_name String Database name identifier. prod_db; sysmaster Required
@debnathbikram debnathbikram added enhancement New feature or request experts needed This issue or pull request is outside an area where general approvers feel they can approve labels Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request experts needed This issue or pull request is outside an area where general approvers feel they can approve triage:needs-triage
Projects
Status: Need triage
Development

No branches or pull requests

1 participant