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

[BUG] - k8s integration ingestion method is not clear enough #201

Open
shaigbdb opened this issue Dec 25, 2024 · 2 comments
Open

[BUG] - k8s integration ingestion method is not clear enough #201

shaigbdb opened this issue Dec 25, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@shaigbdb
Copy link

What is the bug?
We've been able to install the integration dashboards as well as the sample data. However, it is unclear how one is expected to ingest the relevant data.

The repo mentions using OpenTelemetry collectors to collect the data. However, the documentation in the OpenTelemetry website is insufficient for this - I'm getting errors from the opentelemetry pod.

2024-12-12T13:35:10.976Z	error	internal/queue_sender.go:92	Exporting failed. Dropping data.	{"kind": "exporter", "data_type": "logs", "name": "otlp", "error": "not retryable error: Permanent error: rpc error: code = Unimplemented desc = unexpected HTTP status code received from server: 404 (Not Found); transport: received unexpected content-type \"text/plain; charset=utf-8\"", "dropped_items": 1}
go.opentelemetry.io/collector/exporter/exporterhelper/internal.NewQueueSender.func1
	go.opentelemetry.io/collector/[email protected]/exporterhelper/internal/queue_sender.go:92
go.opentelemetry.io/collector/exporter/internal/queue.(*Consumers[...]).Start.func1
	go.opentelemetry.io/collector/[email protected]/internal/queue/consumers.go:43

I've also tried the fluentbit configuration though unfortunately it seems to be irrelevant. The fluentbit kubernetes filter only collects partial data from Kubernetes which does not match the data required by the integration's dashboards (such as the deployment details).

There is a fluent bit issue describing this:

fluent/fluent-bit#9263

The filebeat versions supported by Opensearch have a similar issue, so it is not an option. The other options mentioned in that issue require developing support for the additional fields.

How can one reproduce the bug?
Use attached data prepper and otel configurations in accordance with the documentation.

What is the expected behavior?
Kubernetes integration data being loaded into the cluster.
I would appreciate templates for data prepper and otel (assuming that is the solution) that correctly collect the integration data for k8s.

What is your host/environment?

Thanks.

@shaigbdb shaigbdb added bug Something isn't working untriaged labels Dec 25, 2024
@YANG-DB
Copy link
Member

YANG-DB commented Jan 6, 2025

@shaigbdb - thanks for this feedback !
we will review and propose some documentation on better End2End and possibly (a bit later) a k8s based solution showcasing the entire workflow

@krisfreedain
Copy link
Member

Catch All Triage - 1, 2, 3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants