v1.10.1
⚠️ Compatibility Notice
This version introduces a cluster identifier in data collection to support cluster-level data isolation. If you're upgrading from a previous version:
- Existing data will be assigned to a "default (empty)" cluster.
- Newly collected data will be assigned to the configured cluster during installation.
While most features remain compatible and data display is unaffected, a few features that rely on historical data across clusters may show gaps or inconsistencies. Potentially affected features:
- Alert rules that depend on historical baselines
- AI-powered root cause analysis based on historical patterns
New Features
- Multi-Cluster Support: Enables data isolation and filtering by cluster. Users can specify the target cluster during installation to support precise queries in multi-cluster environments.
- AI-Powered Alert Diagnosis Direction: Automatically identifies potential root causes of alerts using large language models, guiding users quickly toward fault localization.
- Root Cause Analysis Report: After completing alert analysis, the system generates a structured root cause report to help users understand and trace the origin of issues.
- Enhanced Alert Analysis Workflow: Now supports detection of memory leak scenarios and offers deeper insights into issues like high CPU usage, memory pressure, and network latency on hosts.
Enhancements
- Faster Log Queries: Significantly improved the performance of full log retrieval, ensuring faster access to large datasets.
- Improved Alert Analysis Accuracy: Refined AI workflow strategies to enhance diagnosis precision and scenario coverage.
- Enhanced Data Group Management: Supports nested sub-groups to better reflect organizational structures; allows grouping by cluster, namespace, service name, and more for flexible data control.
Bug Fixes
- Fixed an issue where data could not be filtered properly on traditional servers without namespaces.
- Resolved an issue where the polaris metrics might be lost after extended operation.
- Fixed errors occurring when service endpoints contain special characters.
- Resolved time zone inconsistencies that caused baseline misalignment in incident reports.