You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
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:
the user could do the following:
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
The text was updated successfully, but these errors were encountered: