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
Describe your use-case which is not covered by existing documentation.
Though there are ways to configure the Java OTEL SDK to submit logs to OTLP endpoint using environment variables, this functionality is not well documented.
There are clues in the Elastic documentation about settings you can make to accomplish this use case, but it's not straight forward for somebody unfamiliar with the SDK.
It would also be desirable to have these configuration options available in the configuration modal of the plugin.
As I understand it, the following settings will accomplish this task if added to the "Configuration Properties":
Describe your use-case which is not covered by existing documentation.
Though there are ways to configure the Java OTEL SDK to submit logs to OTLP endpoint using environment variables, this functionality is not well documented.
There are clues in the Elastic documentation about settings you can make to accomplish this use case, but it's not straight forward for somebody unfamiliar with the SDK.
It would also be desirable to have these configuration options available in the configuration modal of the plugin.
As I understand it, the following settings will accomplish this task if added to the "Configuration Properties":
The second option there seems to be required if we want to still see the logs in Jenkins instead of only in our observability platform.
Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
There appears to be some considerable documentation here, but it's not very clear:
https://github.com/jenkinsci/opentelemetry-plugin/blob/f8bd70b48ac230e9636f2dc07c24dd3a4ff5f955/docs/build-logs.md#can-pipeline-logs-be-stored-in-other-backends-than-elastic-or-grafana
Are you interested in contributing to the documentation?
No response
The text was updated successfully, but these errors were encountered: