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
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.
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).
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.
@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
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.
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?
data-prepper-k8s.yaml.txt
values.yaml.txt
Thanks.
The text was updated successfully, but these errors were encountered: