Configuring Tiered Monitoring and Debugging in Kyvos

Configuring Tiered Monitoring and Debugging in Kyvos

Kyvos supports a tiered monitoring for the Query Engine and BI server, enabling administrators to choose monitoring levels (Tier 0–4) based on their requirements. These tiers range from basic monitoring with minimal impact to advanced debugging using AddressSanitizer (ASAN). Enabling or disabling sanitization requires safe engine restarts. 

Note

The AddressSanitizer (ASAN) is:

  • Supported only with JRE 17. Download the corresponding ASAN integrated jar and upload it to the Upload External Libraries page.

  • Enabled for tier 3 and tier 4.

Key Highlights

  • Tier Levels (0–4): Select the required monitoring level based on diagnostic requirements.

  • Centralized Logs: All monitoring logs are consolidated into a single downloadable archive.

  • Safe Configurations: Applied via full engine restarts to maintain consistency.

Points to Know

  • Tier-4 Debugging: Requires passwordless sudo access for the Kyvos user on each cluster node.

  • Configuration Path: Navigate to Kyvos Manager > Properties > global.properties and set the following:

    • ANALYTICAL_STORE_MONITORING_TIER (hot deployable)–The property is used to set the debugging tier for Kyvos. Select the required option (None, Tier 1, Tier 2, Tier 3, and Tier 4) from the list. The None option is selected by default as it indicates tier 0 when no system debugging will work.
      Once you set the required tier (Tier 1, Tier 2, Tier 3, or Tier 4) for debugging, the system will run indefinitely until you reset it to Tier 0.

    • ANALYTICAL_STORE_MONITORING_INTERVAL – The property defines the interval in seconds at which the Kyvos system monitoring logs are repeatedly generated. By default, the interval duration 600 seconds is set. You can modify the interval as needed.

You can download all monitoring logs consolidated into a single archive from Monitor > Log files.

Copyright Kyvos, Inc. 2025. All rights reserved.