1. Home
  2. CrossConnect
  3. Modules
  4. Flow Assurance
Optional moduleOperations and support

Flow Assurance

Why is Salesforce slow, and which part of its supporting network should we inspect?

Explore Flow Assurance
The decision momentWhen the question becomes urgent

A named business application is slow or unavailable, and the team needs to trace its supporting network context.

The application owner has a service name while the network team has devices and interfaces. Neither starts with a shared record that connects the application to its supporting path.

An application owner reports that Salesforce is slow. Flow Assurance starts with the named application, then shows its endpoints, the supporting network path, and the health evidence for that path.

What changesThe practical result

Begin with the application, then trace the network evidence that supports it.

  • Connect an observed application to its endpoints, reporting device, and available inferred fabric path.
  • Show whether the available supporting-device health evidence identifies a local fault or leaves the cause unresolved.
Evidence in viewThe evidence it starts with

Trace the application from a flow record to its supporting network evidence.

  • Uses available flow records to name observed applications and their endpoints.
  • Relates the application evidence to reporting-device health and an inferred fabric path when those records are available.
Product viewApplication triage with an incident answer
CrossConnect V1 Flow Assurance application table showing Salesforce, Microsoft Teams, Zoom, and their incident verdicts.
Application triage with an incident answer. Select the image to view full size

Demo controls are loading.

Open the recordSee what the team sees next

Open Flow Assurance in the record.

Open the resulting view, then review the evidence and the next safe action beside it.

Continue the investigationRelated optional modules

Use Iris when the affected service depends on an AV endpoint or its supporting port.