Skip to content
StackHeal

Use cases

Specific Problems. Specific Workflows.

12 operational problems, each with the trigger that starts the workflow, the steps it runs, and what it verifies before closing. Filter by product or by the kind of business you run.

12 of 12 use cases

    • AI Support Automation
    • Infrastructure Monitoring

    Disk space exhaustion on a customer server

    A ticket or alert reports a full or nearly full volume, and an engineer has to log in, find the cause and clear space.

    1. Resolve the ticket or alert to a specific host from inventory
    2. Measure current usage and identify the largest consumers
    3. Apply the cleanup scope approved for that asset class
    4. +1 more step

    See the full workflow

    • VM Provisioning
    • Workflow Orchestration

    Turning an order into a verified running instance

    Provisioning involves a dozen steps across several systems, and a missed step produces a machine that is unmonitored, unprotected or untagged.

    1. Normalise the order into a provisioning specification
    2. Check entitlement, quota and placement policy
    3. Build from the approved template through the platform API
    4. +1 more step

    See the full workflow

    • Backup Automation

    Nightly backup reconciliation across tools

    Backup coverage is spread across several products and consoles, so an asset with no recent copy is invisible until a restore is needed.

    1. Derive the set of assets that should have a copy in the window
    2. Collect outcomes from every backup system
    3. Retry transient failures and escalate structural ones
    4. +1 more step

    See the full workflow

    • Backup Automation
    • Workflow Orchestration

    Scheduled restore testing

    Nobody knows how long a restore takes or whether recovery points are usable, because testing is a project rather than a routine.

    1. Select the next assets in the rotation
    2. Restore to an isolated target
    3. Run integrity and application-level checks for that asset class
    4. +1 more step

    See the full workflow

    • Server Operations

    Rolling patch and reboot across a fleet

    Monthly patching is coordinated by hand, takes a full maintenance window of attention, and stalls when one host misbehaves.

    1. Resolve the target set and preview it before starting
    2. Drain each host, patch, reboot and wait for health
    3. Verify before moving to the next wave
    4. +1 more step

    See the full workflow

    • VM Provisioning

    GPU capacity request with approval and driver verification

    Accelerated capacity is scarce and expensive, and a build with the wrong driver stack wastes both the allocation and the customer's time.

    1. Validate the requested accelerator against live inventory
    2. Hold for approval above a cost threshold
    3. Provision with the correct driver and runtime image
    4. +1 more step

    See the full workflow

    • Infrastructure Monitoring

    Alert arrives with the investigation already done

    Every alert costs an engineer the same twenty minutes of log reading, metric checking and change-history review before they can act.

    1. Correlate related signals into a single incident
    2. Run the read-only checks a first responder would run
    3. Match the pattern against runbooks and past incidents
    4. +1 more step

    See the full workflow

    • Infrastructure Monitoring
    • Workflow Orchestration

    Certificate and expiry management

    Certificates, licences and domains expire on a schedule nobody owns, and the first symptom is an outage.

    1. Detect approaching expiry across the estate
    2. Identify the owning service and tenant
    3. Run the approved renewal workflow
    4. +1 more step

    See the full workflow

    • Workflow Orchestration
    • VM Provisioning

    Onboarding a new customer environment

    Standing up a new customer takes weeks of coordination across billing, provisioning, monitoring, backup and documentation, and never comes out identical.

    1. Create tenant records across every system involved
    2. Provision the agreed resources from approved templates
    3. Apply monitoring and backup policy and verify coverage
    4. +1 more step

    See the full workflow

    • AI Support Automation
    • Workflow Orchestration

    Routine access provisioning with approval

    Access requests wait for the one team holding the credentials, and the record of who approved what is scattered.

    1. Validate the requester against the account contact list
    2. Check the request against the tenant's access policy
    3. Request owner approval where policy demands it
    4. +1 more step

    See the full workflow

    • VM Provisioning
    • Server Operations

    Decommission that leaves nothing behind

    Cancelled services keep consuming capacity and appearing in monitoring, because decommission is a checklist that is rarely finished.

    1. Confirm the asset has no dependent services
    2. Take the final retained copy
    3. Collect owner sign-off
    4. +1 more step

    See the full workflow

    • Workflow Orchestration
    • Server Operations

    Configuration drift detection and ticketing

    Configuration diverges from baseline over time, and the divergence is discovered during an audit or an incident.

    1. Query configuration state across the estate on a schedule
    2. Compare against the expected baseline
    3. Record deviations with asset detail
    4. +1 more step

    See the full workflow

Which of these describes your week?

Tell us the two or three request types that take the most manual effort, and we will map out how each would be automated.

Book a DemoExplore Solutions