-
Notifications
You must be signed in to change notification settings - Fork 2
Garcia/operator with telemetry #27
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
Conversation
… and error handling. Ensure script is run from repository root and provide detailed instructions for accessing Zipkin UI.
- Integrated OpenTelemetry SDK for browser tracing in the client application. - Added necessary dependencies for OpenTelemetry in package.json and package-lock.json. - Updated Dockerfile to include OTEL_COLLECTOR_URL as an environment variable. - Enhanced deployment scripts to set up port-forwarding for the OpenTelemetry collector. - Updated collector image version in values.yaml to 0.141.0. - Improved CORS configuration in the collector's configmap for local development.
- Modified expressions in the dashboard to improve metric aggregation for subgraphs and HTTP requests. - Updated titles and legend formats for clarity in visualizations. - Enhanced README with dashboard requirements, usage instructions, and known limitations regarding HTTP status codes in subgraph metrics.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to build our own dashboard or reference the APM project and link it here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I commented earlier. I much rather look at updating the APM platform and pulling the dashboard from theere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a general comment we could look at substituting these value with labels and deployments
This PR adds a script for setting up tracing and metrics telemetry via an OTEL collector that exports for prometheus to scrape from the collector with a grafana dashboard.
The client ui, router, coprocessor, and subgraphs should all be submitting trace information. The router, coprocessor, and subgraphs should be submitting metric information to be viewed on the grafana dashboard.
The dashboard itself is an early version of the grafana dashboard that I will submit as the updated template in the
apm-templatesrepo for grafana and is based on the Datadog dashboard that was announced at SummitHere is a visual of that dashboard