[Oracle OTel] Add content pack

[agithomas]

• Enhancement

Proposed commit message

Add Oracle Database OpenTelemetry content pack providing dashboards,
alert rules, and SLO templates for monitoring Oracle via the
oracledbreceiver.

WHAT:

• 6 dashboards: Overview, Resource Capacity/Sessions/Locking, SQL Execution/I/O/Cache, Transaction Health/Storage, Active Query Analysis (ASH-equivalent), Query Performance & Plans (AWR-equivalent)
• 10 alert rule templates covering process/session/tablespace/lock utilisation, buffer cache hit ratio, hard parse ratio, rollback
  ratio, and enqueue deadlocks
• 6 SLO templates (timeslice-based, 99.5% over rolling 30 days) for process utilisation, session utilisation, buffer cache hit ratio, hard parse ratio, rollback-to-commit ratio, and zero deadlocks
• Dashboard YAML sources in _dev/shared/kibana
• Customer-facing README with optional metrics configuration, query event setup, and troubleshooting

WHY:
Oracle Database is widely used in enterprise environments and lacks OTel-native observability content in Elastic. This pack gives SREs immediate visibility into Oracle health using the oracledbreceiver
without requiring manual dashboard/alert creation.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• Integration tests using Oracledbreceiver

How to test this PR locally

• elastic-package build && elastic-package stack up -v -d --services package-registry
• Configure the receiver following the settings mentioned in the README.

Screenshots

Overview dashboard

---

SQL Execution dashboard

---

Transaction health

---

Active query analysis

---

Query performance

---

Oracle resource capacity

---

[github-actions]

Vale Linting Results

Summary: 8 warnings, 7 suggestions found

⚠️ Warnings (8)

File	Line	Rule	Message
packages/oracle_otel/docs/README.md	5	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'.
packages/oracle_otel/docs/README.md	156	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'versus' instead of 'vs'.
packages/oracle_otel/docs/README.md	163	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'versus' instead of 'vs'.
packages/oracle_otel/docs/README.md	255	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'versus' instead of 'vs'.
packages/oracle_otel/docs/README.md	256	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'versus' instead of 'vs'.
packages/oracle_otel/docs/README.md	270	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/oracle_otel/docs/README.md	274	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
packages/oracle_otel/docs/README.md	288	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.

💡 Suggestions (7)

File	Line	Rule	Message
packages/oracle_otel/docs/README.md	84	Elastic.WordChoice	Consider using 'deactivated, deselected, hidden, turned off, unavailable' instead of 'disabled', unless the term is in the UI.
packages/oracle_otel/docs/README.md	201	Elastic.Semicolons	Use semicolons judiciously.
packages/oracle_otel/docs/README.md	238	Elastic.WordChoice	Consider using 'select, press, visits' instead of 'hit', unless the term is in the UI.
packages/oracle_otel/docs/README.md	257	Elastic.WordChoice	Consider using 'select, press, visits' instead of 'hit', unless the term is in the UI.
packages/oracle_otel/docs/README.md	257	Elastic.WordChoice	Consider using 'select, press, visits' instead of 'hit', unless the term is in the UI.
packages/oracle_otel/docs/README.md	270	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
packages/oracle_otel/docs/README.md	288	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: e31d206

History

• 💚 Build #39890 succeeded 5f2ed09
• 💚 Build #39883 succeeded abb9c70

[elastic-vault-github-plugin-prod]

Package oracle_otel - 0.1.0 containing this change is available at https://epr.elastic.co/package/oracle_otel/0.1.0/