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

[opentelemetry] production-ready testing OTEL-logs collector #245

Closed
3 of 5 tasks
Tracked by #353
timojohlo opened this issue Jul 25, 2024 · 4 comments
Closed
3 of 5 tasks
Tracked by #353

[opentelemetry] production-ready testing OTEL-logs collector #245

timojohlo opened this issue Jul 25, 2024 · 4 comments
Assignees

Comments

@timojohlo
Copy link
Member

timojohlo commented Jul 25, 2024

Context

Currently we are running OpenTelemetry with only collecting, processing and forwarding a few logs. We want to test OpenTelemetry with production load data including Daemonset. This should not test a cluster but rather OpenTelemetry itself.

Expected to be dragged into Sprint 10/24, since observing will take some time.

Prerequisite

Acceptance Criteria

  • Decide in which cluster to test OpenTelemetry (old landscape)
  • Including grok-parsing
  • Filter to only parse some logs
  • Convert fluent configs to OpenTelemetry configs

References

@timojohlo
Copy link
Member Author

This issue needs more details that can be or need to be discussed in the observability meeting.

@artherd42 artherd42 changed the title [opentelemetry] loadtesting opentelemetry [opentelemetry] production-ready testing OTEL-logs collector Aug 27, 2024
@Kuckkuck
Copy link
Contributor

Kuckkuck commented Sep 2, 2024

postponed, greenhouse has to deploy more stuff to prod to get our opentelemetry plugin also to prod greenhouse. That this can be deployed to the ceph clusters.

@Kuckkuck
Copy link
Contributor

Follow up ticket #407

@viennaa
Copy link
Contributor

viennaa commented Sep 24, 2024

Ticket is too generic, @Kuckkuck to create follow-up tickets for 10/24 Sprint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants