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.

Sign up for GitHub

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

Jump to bottom

PoC OpenTelemetry - logs #562

Closed
a-thaler opened this issue Mar 25, 2021 · 10 comments
Closed

PoC OpenTelemetry - logs #562

a-thaler opened this issue Mar 25, 2021 · 10 comments
Labels
area/logs LogPipeline lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@a-thaler
Copy link
Collaborator

Description

That is the third piece to solve kyma-project/kyma#10119

Motivation:

  • understanding on logs instrumentation inside an app, will the sdk provide a full log framework? Is it required to use the sdk inside the app?
  • understanding of how it is planned to support collecting logs of 3-party-apps where the log outpu/format cannot be influenced, will it be similar to a fluent-bit agent?
  • understanding of current status, what is possible and what is missing in order to start leveraging it
  • validate the overall vision in regards if OTEL can solve the expected problems

High-level outcome:

  • Explain opportunities and weaknesses, what problems can be solved nicely, what problems do you see
  • Demo log instrumentation in action, demonstrate how it contributes to our journey
  • blueprint: step-by-step guide on how to setup a playground based on the blueprint from (#10873 ) with one application exposing logs and correlating it with traces

Technical goals:

  • What log protocols are supported by the OTEL sdk? How to integrate with existing application where the log output is fixed
  • Try to use the OTEL format for communication to the collector, any problems
  • How to enrich the logs with trace info

Reasons

Attachments
@a-thaler a-thaler mentioned this issue Mar 25, 2021
Closed
@ghost
Copy link

ghost commented Jun 11, 2021

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

3 similar comments
@ghost
Copy link

ghost commented Aug 13, 2021

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost
Copy link

ghost commented Oct 15, 2021

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost
Copy link

ghost commented Dec 17, 2021

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost
Copy link

ghost commented Dec 24, 2021

This issue has been automatically closed due to the lack of recent activity.

@ghost ghost closed this as completed Dec 24, 2021
@ghost
Copy link

ghost commented Mar 15, 2022

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 15, 2022
@a-thaler a-thaler removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 15, 2022
@ghost
Copy link

ghost commented May 14, 2022

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 14, 2022
@a-thaler a-thaler removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 16, 2022
@ghost
Copy link

ghost commented Jul 15, 2022

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 15, 2022
@a-thaler a-thaler removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 15, 2022
@github-actions
Copy link

github-actions bot commented Oct 9, 2022

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 9, 2022
@a-thaler a-thaler added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 10, 2022
@a-thaler a-thaler transferred this issue from kyma-project/kyma Nov 20, 2023
@a-thaler a-thaler added area/logs LogPipeline and removed area/logging labels Nov 20, 2023
@a-thaler
Copy link
Collaborator Author

Replaced by #556

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/logs LogPipeline lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@a-thaler @rakesh-garimella