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

Provide additional configuration options for OracleDB connection information #22087

Closed
crobert-1 opened this issue May 18, 2023 · 0 comments
Closed
Labels
enhancement New feature or request receiver/oracledb

Comments

@crobert-1
Copy link
Member

Component(s)

receiver/oracledb

Is your feature request related to a problem? Please describe.

This is a UX enhancement request. Currently in the OracleDB receiver config, a user must define an option called the datasource. This is a string formatted in a specific way and used to connect to the OracleDB instance that the collector will receive metrics from.

This can be a difficult UX as users may not understand the format of the string, or how to use it.

Describe the solution you'd like

Rather than a single datasource string, the receiver should be able to take the actual information in single pieces that make sense to the user, and then format it as the connection string internally.

So, instead of:

receivers:
  oracledb:
    datasource: "oracle://otel:password@localhost:51521/XE"

the user could do the following:

receivers:
  oracledb:
    endpoint: localhost:51521
    password: password
    service: XE
    username: otel

This is simpler to understand as an end-user, as well as a developer. The best UX here in my opinion is to allow the user to choose either config option. If both are defined the original datasource string will be used.

Describe alternatives you've considered

An alternative would be to force users to use the new broken up data source string (the new config option where each connection variable is defined independently), instead of the original single string option. This could technically work since this receiver is in alpha, but I think overall this wouldn't be a great user experience. There may also be users who end up preferring the single datasource string option as well, so this would get in their way.

Additional context

No response

@crobert-1 crobert-1 added enhancement New feature or request needs triage New item requiring triage labels May 18, 2023
@atoulme atoulme added receiver/oracledb and removed needs triage New item requiring triage labels May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request receiver/oracledb
Projects
None yet
Development

No branches or pull requests

2 participants