Hariz Hasecic

Ok thank you for the reply! No need to apologize friend. Your work is really impressive and I am extremely impressed by how far you cave gotten so far and...

> You can already do that by using the templates :) https://github.com/opensearch-project/opensearch-k8s-operator/blob/main/charts/opensearch-operator/files/opensearch.opster.io_opensearchindextemplates.yaml Might be worth trying creating your indexes with the "curator" like this : https://github.com/flant/curator-opensearch/blob/main/examples/actions/create_index.yml

@KarstenSchnitter That is a very good way of re-phrasing my request. I think you might be right. The "serviceGraphConnector" looks like its doing the right thing. It seems to be...

About Alias: I didn't touch the alias. Only removed index. Log message: I think it said that the index is missing. I'll reproduce the bug again later when I have...

Did you want to do this because OpensearchDashboards cannot visualize nested fields?

The certmanager documentation recommends people to use this when syncing various configurations with their workloads: https://github.com/wave-k8s/wave I haven't tried out though. But i'm looking for a solution on how to...

I think the OtelCollectors "opensearch exporter" sends things via http instead of using grpc websockets. Have you tried it? https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/opensearchexporter

They should focus on making it faster, so it can be generated in realtime (turboXL) using only a 4090. That is key to making it spread out. If they require...

Cool idea. But why settle with painless. Why not just offer LUA scripting in general? Seems like an easier solution.

Good Idea, but bad name. I propose "Opensearch Collector" as a new name. This way when people use "OpenTelemetry Collector" they will be reminded of opensearch since both offer collectors...