elastic / elastic/integrations

[LogsDB] [Stack 8.19.20-SNAPSHOT] [oracle] Failing test daily: system test: (elastic-agent logs - systemstatistics) in oracle.system_statistics

Open
#20,501 0 comments 0 reactions 0 assignees View on GitHub
automation flaky-test Integration:oracle
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
2d 17h
Merged PRs (30d)
225

Description

- Stack version: 8.19.20-SNAPSHOT
- LogsDB: enabled
- Package: oracle
- Failing test: system test: (elastic-agent logs - systemstatistics)
- DataStream: system_statistics
- Owners:
- @elastic/obs-infraobs-integrations

Failure:
```
test case failed: one or more errors found while examining elastic-agent.logs3701419342: [0] found error "Unit state changed sql/metrics-default-sql/metrics-oracle-4b41ce59-42b0-43da-b7a6-df97766a2b01 (HEALTHY->DEGRADED): Error fetching data for metricset sql.query: cannot open connection: testing connection: user=\"sys\" standalone params={authMode:2 connectionClass: connectionClassLength:0 purity:0 newPassword: newPasswordLength:0 appContext: numAppContext:0 externalAuth:0 externalHandle: pool: tag: tagLength:0 matchAnyTag:0 outTag: outTagLength:0 outTagFound:0 shardingKeyColumns: numShardingKeyColumns:0 superShardingKeyColumns: numSuperShardingKeyColumns:0 outNewSession:0}: ORA-12541: TNS:no listener"
```

First build failed: https://buildkite.com/elastic/integrations/builds/47076

Latest 5 failed builds:
- https://buildkite.com/elastic/integrations/builds/48320
- https://buildkite.com/elastic/integrations/builds/48399
- https://buildkite.com/elastic/integrations/builds/48456
- https://buildkite.com/elastic/integrations/builds/48531
- https://buildkite.com/elastic/integrations/builds/48613

Contributor guide

Open the contributing guide

Research direction

Start with the failing `system test: (elastic-agent logs - systemstatistics)` for the `oracle` package and compare the linked Buildkite failures. Investigate why the Oracle `sql.query` metricset cannot connect because of `ORA-12541: TNS:no listener`; done means the test passes in subsequent builds without the connection error.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
databases, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.