Skip to content

Disk Space Management

Source: Disk Space Management: RaaS & Envoy (TRIB 20144095233)

This page describes how disk space utilisation is managed for RaaS and Envoy customers. By design, RaaS customers operate a self-service model and are responsible for managing their own disk space.

Envoy customers

Envoy customer agreements cover infrastructure deployment. Disk space is managed by GOT with no customer engagement required. Coordinate via the Envoy <> GoT Escalation MS Teams channel.

Thresholds and Actions

Disk Space Utilisation Action
< 80% No action needed
80–90% Alert triggered; monitor. May proactively notify if trending toward 90% before a weekend/holiday
> 90% Notification triggered → create OPS Jira + SalesForce case → notify Support team → Support contacts customer
> 95% (Prod only) GOT adds disk space in increments to get customer under 90%; escalate OPS Jira to P2

Threshold Exception — pre-weekend notification

If a customer is at 89% on a Friday and trending upward, notify proactively before the weekend. Add note: "The environment threshold is forecasted to meet the 90% threshold during a non-business day."

Response Process (When > 90%)

  1. GOT creates an OPS Jira (Cloud Ticket, appropriate priority)
  2. Add screenshots of disk usage and directory breakdown
  3. GOT posts in the Global Ops - Cloud Teams channel to notify Support
  4. Support sends one notification to the customer with KB links for self-management
  5. Support sets SalesForce case to auto-close after notification
  6. For Production environments: GOT continues monitoring; adds disk space if trajectory indicates imminent outage
  7. For Non-Production environments: no further monitoring or disk additions after initial notification

Disk Space Addition Guidelines (Production > 95%)

Customer Size Increment to Add
Small +50 GB
Medium +100 GB
Large/XL Multiples of 100 GB

General guidance: add 5% of current disk size to keep customer ≤ 90%. Add a FinOps label to the OPS Jira.

Notify Sales/AM of the addition to create an amendment (if they don't pay, Sales creates a $0 SFO).

Common Causes of High Disk Usage

  1. High message load — volume or size of messages exceeding normal levels
  2. Large messages — HL7 is usually a few KB, but CCD/XML/DICOM can be much larger
  3. Long archive retention — default 14 days; longer periods fill disk faster
  4. Messages stuck in queues — a single message in a comm point queue, route queue, error queue, or hold queue can use ~25 MB (not eligible for cleanup while queued)
  5. Excessive message transformations — each filter that modifies a message writes to the datastore; a 1 MB message modified 10 times = 10 MB used
  6. Non-recommended config practices — e.g., storing a full message body in a message property

Customer Self-Service KB Articles

Share these with customers when notifying them:

Special Customer Notes

Customer Disk Management Rule
I-Med Envoy rules for DICOM environments; RaaS rules for all others

Tools