Overview
The article discusses the latest updates in ClickStack, an open-source observability stack built on ClickHouse, highlighting the introduction of native JSON support for improved query performance and flexibility in handling observability data. It also acknowledges new contributors and outlines additional enhancements to the stack, including Helm chart improvements and CSV download capabilities.
What You'll Learn
1
How to enable JSON support in ClickStack for better observability data handling
2
Why using the JSON type improves query performance in ClickHouse
3
When to utilize the new features in HyperDX for enhanced UI interactions
Key Questions Answered
What are the benefits of using the JSON type in ClickStack?
The JSON type allows for faster queries, improved scalability, and better handling of semi-structured data in ClickStack. It preserves data types, reduces I/O, and enables intuitive querying of nested data structures, making observability solutions more efficient.
How can users enable JSON support in ClickStack?
To enable JSON support in ClickStack, users need to set two environment variables when deploying the stack: `BETA_CH_OTEL_JSON_SCHEMA_ENABLED=true` and `OTEL_AGENT_FEATURE_GATE_ARG='--feature-gates=clickhouse.json'`. This allows the stack to handle JSON data natively.
What improvements have been made to the HyperDX Helm chart?
Recent enhancements to the HyperDX Helm chart include the ability to use custom MongoDB services, support for custom ClickHouse user credentials, improved PVC configuration, and expanded ingress capabilities. These updates provide users with more flexibility in their deployments.
What is the performance improvement seen with the new JSON type?
Queries using the new JSON type in ClickStack can be up to 9 times faster compared to the previous Map type. This significant speedup is due to reduced I/O and the preservation of data types, allowing for more efficient data retrieval.
Key Statistics & Figures
Query performance improvement
up to 9x faster
This improvement is observed when comparing the new JSON type to the previous Map type in ClickStack.
Docker image size reduction
from 3GB to 2.2GB
This reduction enhances the user experience by making the getting started process faster and more efficient.
Technologies & Tools
Some links below are affiliate links. We may earn a commission if you make a purchase.
Database
Clickhouse
Used as the underlying engine for the ClickStack observability stack.
Data Collection
Opentelemetry
Employed for data collection in ClickStack, allowing for flexible observability data ingestion.
Frontend
Hyperdx
Serves as the UI layer for ClickStack, providing visual exploration of observability data.
Deployment
Helm
Used for managing Kubernetes applications and enhancing ClickStack deployments.
Key Actionable Insights
1Implement the JSON type in your ClickStack deployment to enhance query performance and flexibility.By utilizing the JSON type, you can significantly reduce I/O operations and improve the speed of your queries, especially when dealing with high-cardinality data.
2Leverage the enhancements in the HyperDX Helm chart to customize your observability stack.These improvements allow for better integration with existing infrastructure and can help streamline your deployment process, making it easier to manage resources.
3Consider migrating from the Map type to JSON for existing observability data.Migrating to the JSON type will not only improve performance but also simplify your data structure, making it easier to work with and query.
Common Pitfalls
1
Failing to migrate existing data from the Map type to the new JSON type can lead to performance issues.
Without migration, users may continue to experience slower queries and increased I/O due to the limitations of the Map type, which does not handle nested data efficiently.
Related Concepts
Observability Best Practices
Data Schema Design In Clickhouse
Opentelemetry Integration Strategies