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
Is your feature request related to a problem?
We are currently running OpenSearch and OpenSearch Dashboard, but we have not deployed DataPrepper. The spans are being stored in OpenSearch, but since we haven't deployed DataPrepper we are missing out of the service map feature in OpenSearch Dashboards.
What alternatives have you considered?
Alternatives are Grafana Tempo, but then we probably drop OpenSearch Dashboards and rather use Grafana's stack. Jaeger's System Architecture diagrams.
Do you have any additional context?
Given that we are an ISV we would like to keep the deployment as simple as possible and we have worked with getting OpenTelemetry Collector Contrib setup to handle autoscaling and making the deployment robust. Since we know that this takes time we would like to avoid having to do the same for DataPrepper.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
We are currently running OpenSearch and OpenSearch Dashboard, but we have not deployed DataPrepper. The spans are being stored in OpenSearch, but since we haven't deployed DataPrepper we are missing out of the service map feature in OpenSearch Dashboards.
What solution would you like?
I would like to be able to setup OpenTelemetry Collector Contrib's Service Graph Connector and through that be able to get service maps in OpenSearch Dashboard.
What alternatives have you considered?
Alternatives are Grafana Tempo, but then we probably drop OpenSearch Dashboards and rather use Grafana's stack. Jaeger's System Architecture diagrams.
Do you have any additional context?
Given that we are an ISV we would like to keep the deployment as simple as possible and we have worked with getting OpenTelemetry Collector Contrib setup to handle autoscaling and making the deployment robust. Since we know that this takes time we would like to avoid having to do the same for DataPrepper.
The text was updated successfully, but these errors were encountered: