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
While exploring the OpenTelemetry Collector repository, I noticed several custom exporters built to suit specific use cases. Inspired by this, I am proposing the development of a custom OpenTelemetry exporter tailored for DiceDB.
Benefits:
Enhanced Observability:
A custom exporter will allow DiceDB users to efficiently send telemetry data (e.g., metrics, traces, and logs) to their preferred observability tools, enhancing monitoring and debugging capabilities.
Seamless Integration:
The exporter can be fine-tuned to handle DiceDB-specific telemetry formats, ensuring smooth integration into existing OpenTelemetry pipelines.
Improved Performance Insights:
By aligning the exporter with DiceDB's architecture, users will gain deeper insights into performance bottlenecks and overall database health.
Questions for Discussion:
Use Cases: Would this be a valuable addition for current DiceDB users?
Target Systems: What telemetry backends should the exporter support by default (e.g., Prometheus, Elastic, etc.)?
Community Need: Are there existing requests or known needs for observability tools that justify building this exporter?
I’d appreciate input from the community and maintainers on the feasibility and priority of this feature. If this idea aligns with the project goals, I am happy to contribute to its development.
Looking forward to your thoughts!
The text was updated successfully, but these errors were encountered:
While exploring the OpenTelemetry Collector repository, I noticed several custom exporters built to suit specific use cases. Inspired by this, I am proposing the development of a custom OpenTelemetry exporter tailored for DiceDB.
Benefits:
Enhanced Observability:
A custom exporter will allow DiceDB users to efficiently send telemetry data (e.g., metrics, traces, and logs) to their preferred observability tools, enhancing monitoring and debugging capabilities.
Seamless Integration:
The exporter can be fine-tuned to handle DiceDB-specific telemetry formats, ensuring smooth integration into existing OpenTelemetry pipelines.
Improved Performance Insights:
By aligning the exporter with DiceDB's architecture, users will gain deeper insights into performance bottlenecks and overall database health.
Questions for Discussion:
I’d appreciate input from the community and maintainers on the feasibility and priority of this feature. If this idea aligns with the project goals, I am happy to contribute to its development.
Looking forward to your thoughts!
The text was updated successfully, but these errors were encountered: