Quix Cloud Monitoring: May 2025 Release

🌱 New Features 🌱

Clusters Monitoring

‍Introduced Clusters Monitoring, allowing users to track CPU, memory, disk, and pod usage across all available clusters in the organization. The UI provides a summary for a quick overview and historical visualizations with filtering, grouping, and time range options.

‍

⚠ After the release, you’ll need to restart your deployments for usage metrics to start flowing into Clusters Monitoring. Navigate to your Environment ▸ Deployments, open the ⋯ (three-dots) menu, and select Restart deployments.

💎 Enhancements 💎

• Deployments:
  • Improved environment provisioning by using a more secure and traceable method (CRD) for creating namespaces. This change enhances reliability, auditability, and access control across deployments.
  • Improved reliability when deleting pods during delete deployments by preventing cluster operations from hanging indefinitely.
  • Improved performance and stability of deployment logs by limiting how much log data can be retrieved at once and how many log requests run at the same time.
  • Improved handling of out-of-resource errors during deployment.
• Topics:
  • Topic creation uses now one less in-sync replica than the total number of Kafka cluster replicas. This gives more flexibility and helps avoid outages when one broker goes down. If not set manually.
  • Topic management service can now better detect when Kafka is unreachable or times out, preventing operations from getting stuck in a pending state.
• Projects:
  • Optimized sync process to avoid marking the environment as "Failed" when the first operation fails and results in no changes.
• Other:
  • Added support for handling External Source and External Destination definitions directly in the YAML to ensure they persist correctly after syncing.
  • Added the ability to edit cluster name and description in the Environment settings.

🦠 Bug Fixes 🦠

• Online IDE:
  • Sessions now fail faster when resources aren’t available, with clearer error messages to help users understand and resolve the issue more easily.
  • Improved resource handling for IDE Sessions Service to address high CPU spikes and excessive memory usage, ensuring more stable performance during usage peaks.
  • Resolved an issue where IDE sessions could crash if the project's Git reference wasn’t properly set.
• Deployments:
  • When a deployment is updated to remove state management, the associated state configuration is now correctly cleared from the database.
  • Fixed an issue where deployments from commit history were not correctly using the selected commit reference.
• Topics:
  • Fixed an issue where updating a linked topic’s workspaceId using a YAML variable showed the correct changes in the Sync dialog but failed to persist them in the database.
  • Fixed an issue where real-time metrics failed after increasing the number of partitions
• Scratchpads:
  • Fixed an issue where locked Scratchpad deployments without multiline settings could block sync operations.
  • Updated the Scratchpad topic selection to display only linkable topics, avoiding errors on synchronization.
  • Addressed a problem where deleting a locked deployment from YAML didn’t remove it from the database.
  • Relaxed locking conditions in the Scratchpad graph to prevent unnecessary deployment locks.
• Projects:
  • Fixed a problem where users with Manager role couldn't sync projects due to lacking access to organization container registries.
• Other:
  • Fixed an issue where the secrets management dropdown appeared in the wrong location when configuring connectors

‍