elastic / elastic/integrations
[Stack 8.19.22-SNAPSHOT] [oracle] Failing test daily: system test: (elastic-agent logs - sysmetric) in oracle.sysmetric
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 209
Description
- Stack version: 8.19.22-SNAPSHOT
- Package: oracle
- Failing test: system test: (elastic-agent logs - sysmetric)
- DataStream: sysmetric
- Owners:
- @elastic/obs-infraobs-integrations
Failure:
```
test case failed: one or more errors found while examining elastic-agent.logs941149663: [0] found error "Unit state changed sql/metrics-default-sql/metrics-oracle-c16ed8f6-c89a-46aa-be74-607d4962ec9c (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/49549
Contributor guide
Research direction
Start with the oracle package's sysmetric DataStream system test and the first failed build, then investigate the ORA-12541 no-listener error reported while fetching the sql.query metricset. Done means the elastic-agent logs check for this test no longer reports the connection failure.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100