Skip to content

also support SIDs when getting instance from Oracle jdbc connections - #2709

Merged
SylvainJuge merged 3 commits into
elastic:mainfrom
wolframhaussig:support-sid
Jul 28, 2022
Merged

SylvainJuge merged 3 commits into
elastic:mainfrom
wolframhaussig:support-sid

Conversation

@wolframhaussig

@wolframhaussig wolframhaussig commented Jul 11, 2022 •

Copy link
Copy Markdown
Contributor

What does this PR do?

I found that the Kibana service map only shows services of oracle database with its name when using the service_name. When connecting using the SID it only shows as oracle.
Possible workaround: Set the servicename for the database and use the servicename

This PR gathers the low-hanging fruit: It reads the instance from the SID the same way as from SERVICE_NAME.

To discuss: This really was the lowhanging fruit - as the SID (e.g. DB instead of servicename DB.COMPANY.COM) may not be unique. I am not sure if we should add the hostname to the instance to make it unique - e.g. host:port/SID - what o you think?

Checklist

  • This is an enhancement of existing features, or a new feature in existing plugins
    • I have updated CHANGELOG.asciidoc
    • I have added tests that prove my fix is effective or that my feature works
    • I have made corresponding changes to the documentation

@github-actions

Copy link
Copy Markdown

👋 @wolframhaussig Thanks a lot for your contribution!

It may take some time before we review a PR, so even if you don’t see activity for some time, it does not mean that we have forgotten about it.

Every once in a while we go through a process of prioritization, after which we are focussing on the tasks that were planned for the upcoming milestone. The prioritization status is typically reflected through the PR labels. It could be pending triage, a candidate for a future milestone, or have a target milestone set to it.

@github-actions github-actions Bot added community Issues and PRs created by the community triage labels Jul 11, 2022
@ghost

ghost commented Jul 11, 2022 •

Copy link
Copy Markdown

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-07-28T07:27:07.875+0000

  • Duration: 49 min 17 sec

Test stats 🧪

Test Results
Failed 0
Passed 3054
Skipped 36
Total 3090

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • run benchmark tests : Run the benchmark tests.

  • run jdk compatibility tests : Run the JDK Compatibility tests.

  • run integration tests : Run the Agent Integration tests.

  • run end-to-end tests : Run the APM-ITs.

  • run windows tests : Build & tests on windows.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@SylvainJuge SylvainJuge self-assigned this Jul 11, 2022
@SylvainJuge
SylvainJuge self-requested a review July 11, 2022 11:55

@SylvainJuge SylvainJuge left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think for now it should be fine to just capture the SID to provide better granularity when only SID is used.

Regarding the non-uniqueness of the SID and the visible impact in Kibana map, it is something that also happens with other databases when the same database name is used on two distinct hosts or in a clustered database, they will be displayed as if it was a single node. This is a known limitation of the current approach, thus I think that merging this contribution as-is should already provide some benefit for your use-case.

@SylvainJuge
SylvainJuge enabled auto-merge (squash) July 27, 2022 15:47
@SylvainJuge

Copy link
Copy Markdown
Member

@elasticmachine run elasticsearch-ci/docs

@SylvainJuge
SylvainJuge merged commit ca58644 into elastic:main Jul 28, 2022
@wolframhaussig
wolframhaussig deleted the support-sid branch August 1, 2022 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent-java community Issues and PRs created by the community triage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants