About the Capacity app

Note

Version 1.0.0 marks the General Availability (GA) of the ITRS Analytics Capacity app, transitioning from its Beta phase into a fully supported, production-ready release.

The Capacity app version 1.0.0 must be used with ITRS Analytics Platform version 2.16.0 or later.

Proactive capacity management with ITRS Analytics Copied

The ITRS Analytics Capacity app is a real-time capacity monitoring, forecasting, and reporting application designed to provide operational transparency and predictive insights for infrastructure management. This app enables organizations to proactively plan for capacity needs, identify potential capacity breaches before they occur, and maintain compliance with regulatory requirements such as SEBI (Securities and Exchange Board of India) capacity management guidelines.

This Capacity app reports provide operational transparency and predictive insights essential for SEBI-aligned compliance reporting. By tracking both historical performance and forecasted utilization, organizations can maintain service continuity and demonstrate proactive compliance with SEBI’s capacity management guidelines.

Target users Copied

The Capacity app is designed for the following user personas. This is just an example of targeted personas and is not limited to the roles listed below. It may vary depending on the business organization.

This section highlights the key business benefits and operational advantages delivered by the product. It explains how the solution adds value to users, supports organizational goals, and addresses specific challenges or requirements.

Integration with ITRS Analytics ecosystem Copied

Unlike standalone capacity management tools, ITRS Analytics Capacity app is purpose-built for the ITRS Analytics platform, providing:

Real-time continuous monitoring Copied

While traditional capacity tools rely on periodic snapshots, Capacity app offers:

Intelligent breach detection Copied

Sophisticated multi-level alerting system:

Flexible and extensible configuration Copied

Business use case example Copied

Scenario: A stock exchange operates 100 trading servers and must comply with SEBI capacity reporting requirements.

Issues:

Solution with ITRS Analytics Capacity app:

  1. Configure capacity monitoring for CPU, memory, disk, and network across all 100 servers.
  2. Set up automated monthly report generation with daily and weekly bucket analysis.
  3. Enable real-time breach alerting with 75% threshold.
  4. Forecast 60 days ahead to identify servers approaching capacity limits.

Expected results:

Scenario: Track disk space utilization on storage servers and forecast when disks will reach 80% capacity to plan for storage expansion.

Configuration steps:

  1. Create configuration “Storage Disk Capacity”.
  2. Filter entities: type = "storage" AND datacenter = "DC1".
  3. Metrics:
    • Installed Capacity: storage.disk_total_bytes (bytes).
    • Current Usage: storage.disk_used_bytes (bytes).
  4. Sustained peak: 1 hour (MAX aggregation).
  5. Capacity breach threshold: 80%.
  6. Forecast length: 90 days.
  7. Metadata columns: datacenter, rack_id, mount_point.

Report insights:

Expected outcomes:

Scenario: Monitor network throughput on trading platform servers to ensure adequate bandwidth during peak trading hours and comply with SEBI requirements.

Configuration steps:

  1. Create configuration “Trading Network Capacity”.
  2. Filter: service = "stock-exchange" AND tier = "trading".
  3. Metrics:
    • Installed Capacity: Constant 1 GB/s (1,000,000,000 bytes/sec).
    • Current Throughput: network.throughput_bytes_per_sec.
  4. Sustained peak window: 10 seconds (MAX).
  5. Capacity breach threshold: 75% (750 MB/s).
  6. Calendar: “Trading Hours 9:15am-3:30pm Weekdays”.
  7. Forecast: 30 days.

Report analysis:

Expected outcomes:

Create a Capacity configuration Copied

Capacity configurations define what metrics to monitor, how to calculate capacity, and breach detection thresholds.

  1. Navigate to ITRS Analytics Web Console > Capacity app.

  2. In the configurations page, click View Configurations.

  3. Click Create Configuration and provide configuration details.

    Configuration Copied

    Field Description Example
    Name Human-readable name. “Production Server CPU Capacity”
    Entity Filter Expression to select entities. type = "server" AND environment = "production"
    Metrics List of metrics to monitor. See metric configuration below
    Metadata Entity attributes to include in report. region, datacenter, hostname
    Duration (days) Historical lookback period. 180 (default)
    Forecast Length (days) Forecast future period. 60 (default)
    Calendar Business calendar for calculations. “Trading Hours 9am-3:30pm”
    Capacity Breach Threshold Percentage threshold for breach detection. 0.75 (75%, default)
    Projected Peak Multiplier Multiplier for required capacity calculation. 1.5 (default)
    Bucket Interval Local storage aggregation interval. 5 minutes (default)
    Minimum Forecast Days Minimum data required for forecasting. 7 (default)

    New configuration

    Metrics Configuration Copied

    Field Description Options
    Installed Capacity Maximum capacity available
    • Metric: system.cpu_cores
    • Attribute: system.total_memory
    • Constant: 100 (with unit)
    Current Usage Metric Metric tracking current usage system.cpu_usage
    Sustained Peak Window Rolling window for peak calculation 10 seconds, 1 minute, 5 minutes, 1 hour, etc.
    Sustained Peak Aggregation Aggregation function MAX, MIN, AVG, SUM
    Real-Time Monitoring Enable breach alerting true/false (default: false)

    New metrics configuration

  4. Click Save Configuration.

Generate reports Copied

  1. Navigate to Reports page.

  2. Click Create Report.

  3. Choose report parameters:

    • Report Name — for example, “Q1 2025 Capacity Report”.
    • Bucket SizeDaily, Weekly, or Monthly.
    • Configurations - name of the Capacity configuration.
    • Expirate Date
  4. Click Run Report.

    Generate reports

Report generation process:

View reports Copied

  1. Wait until the Capacity configuration status shows Completed.

  2. In the Actions column, click View report.

    View reports

    The table below defines each column and explains its relevance to SEBI-aligned capacity monitoring:

    Column Description
    Metric Name Displays the monitored entity or metric, such as cpuUtilisation_aggregated or memoryUsedPercent_aggregated.
    Historical Peak Shows the maximum utilization percentage recorded for the selected metric over the monitoring period. This highlights whether a Capacity Usage Breach has occurred — when utilization exceeds defined operational thresholds (for example, 80%, 90%, or 100%). It also correlates with Required Capacity Breach, which reflects the projected additional capacity needed to prevent future breaches.
    Peak Occurred Indicates when the last utilization peak occurred (for example, 2 days ago).
    Forecast Predicts future utilization trends based on continuous data ingestion.
    Breach Expected Estimates when a resource is expected to exceed its capacity threshold.
    Required Capacity Shows the projected percentage increase in capacity needed to prevent breaches.
    Category Identifies the infrastructure or business service associated with the metric.
  3. Use Search rows to perform a free-text search across metadata columns.

  4. Toggle Show triggered only to display only the rows with capacity breaches.

Export reports Copied

  1. Open the report and click Export.
  2. Download CSV file with report data. CSV includes all columns and respects applied filters.

Troubleshooting Copied

Reports are not generating Copied

Issues:

Resolution:

  1. Check daemon logs:

    kubectl logs -n itrs deployment/iax-app-capacity-daemon
    
  2. Verify metric data is available:

    a. Ensure entities match entity filter.

    b. Confirm metrics are being collected by platform.

    c. Check that at least 5 minutes of data has been collected (one bucket interval).

  3. Verify configuration:

    a. Review entity filter expression.

    b. Confirm metric names and namespaces are correct.

Forecasts are not appearing Copied

Issue: Reports show data but no forecasted values

Resolution:

  1. Check minimum_forecast_days configuration (default: 7 days).
  2. Ensure sufficient historical data has been collected (7+ days).
  3. Review daemon logs for forecast calculation errors.
["ITRS Analytics"] ["ITRS Analytics > Capacity"] ["User Guide"]

Was this topic helpful?