-
Notifications
You must be signed in to change notification settings - Fork 888
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
Project Tracking: OpenTelemetry configuration #2920
Comments
In Python SIG, we discussed implementing something like Django settings.py for configuration but put it on hold since this idea surfaced. I will be glad to participate in this effort and help the group. |
As mentioned on #1773 I am very interested in this topic and happy to participate. I will not be able to attend calls on Fridays, but hopefully there will be some means for asynch communication! |
I'd like to sponsor this project as a TC member. |
Added to calendar. Doc link: https://docs.google.com/document/d/1uNgWQLQZcSVfBLRXfW9XCVJmKa5NH9R15fSOXhmpGWw/edit |
Thank you @dyladan! |
@codeboten I'm interested in joining the working group and can help contribute a .NET prototype (probably will collaborate with @alanwest on it). |
no-code configuration would be the requirement for the OpenTelemetry C++ to support dynamic loading of SDK. I can help in prototyping for C++ (though it is not mentioned as part of deliverables). |
This OTEP is the result of the Configuration working group. See open-telemetry/opentelemetry-specification#2920 for additional details. cc @MrAlias @jack-berg Signed-off-by: Alex Boten <[email protected]>
This OTEP is the result of the Configuration working group. See open-telemetry/opentelemetry-specification#2920 for additional details. cc @MrAlias @jack-berg Signed-off-by: Alex Boten <[email protected]>
* Configuration proposal This OTEP is the result of the Configuration working group. See open-telemetry/opentelemetry-specification#2920 for additional details.
Does this project include configuration extendibility for vendor specific items? For instance, will Azure be able to configure Connection String and Lightstep configure their access token through this schema? |
* Configuration proposal This OTEP is the result of the Configuration working group. See open-telemetry/opentelemetry-specification#2920 for additional details.
Closing as we have moved to project files and project boards as our way of defining and tracking projects. |
* Configuration proposal This OTEP is the result of the Configuration working group. See open-telemetry#2920 for additional details.
* Configuration proposal This OTEP is the result of the Configuration working group. See open-telemetry/opentelemetry-specification#2920 for additional details.
* Configuration proposal This OTEP is the result of the Configuration working group. See open-telemetry/opentelemetry-specification#2920 for additional details.
* Configuration proposal This OTEP is the result of the Configuration working group. See open-telemetry/opentelemetry-specification#2920 for additional details.
* Configuration proposal This OTEP is the result of the Configuration working group. See open-telemetry#2920 for additional details.
* Configuration proposal This OTEP is the result of the Configuration working group. See open-telemetry/opentelemetry-specification#2920 for additional details.
* Configuration proposal This OTEP is the result of the Configuration working group. See open-telemetry/opentelemetry-specification#2920 for additional details.
Description
OpenTelemetry specifies code that can operate in a variety of ways based on the end-user’s desired mode of operation. This requires a configuration interface be provided to the user so they are able to communicate this information. Currently, OpenTelemetry specifies this interface in the form of environment variables. This environment variable interface is limited in the structure of information it can communicate and the primitives it can support.
The configuration project intends to produce the specification around the data model for language-agnostic configuration that provides additional flexibility for the end users.
Project Board
https://github.com/orgs/open-telemetry/projects/38
Deliverables
Staffing / Help Wanted
End users of OpenTelemetry to help validate the usage and configuration scenarios would be great to have participate in the discussions.
Required staffing
Project lead
Sponsoring TC members
Engineers contributing to the working group
Maintainers and approvers
Meeting Times
Every 2 weeks, on Fridays at 10:30AM PT
Timeline
3-6 months
Labels
The tracking issue should be properly labeled to indicate what parts of the specification it is focused on.
Linked Issues and PRs
All PRs, Issues, and OTEPs related to the project should link back to the tracking issue, so that they can be easily found.
_FILE
variations to support reading from files #2739The text was updated successfully, but these errors were encountered: