Application-Location Rollup

Riverbed IQ correlates multiple Application-Location indicators into a single incident. Collating multiple indicators into a single incident reduces noise and allows for faster, more efficient resolution of the corresponding problems. To implement this, IQ includes triggers, ready-to-use runbooks for automated investigations, and incident types tailored to these events.

Automation Management Page

The Automation Management page provides two Incident triggers for Application-Location issues:

  • Multiple Application - Location Issue — Executes when multiple applications have exhibited performance degradation for users at a specific location around the same time. For example, this event would be triggered if applications like Salesforce, Concur, DocuSign, and Payroll all experienced performance issues at the same time for users in the San Francisco area.

  • Application Multi-Location Issue — Executes when an application has exhibited performance degradation for users at various locations around the same time. For example, this event would be triggered if an application like Salesforce experienced performance issues for users in San Francisco, Dallas, and Boston all at the same time.

You can customize the Triggers by enabling or disabling them to align with your environment and specific requirements. By customizing Triggers, IQ can initiate targeted automations based on unique criteria, enabling customized responses to specific scenarios.

The default triggers for both the Multiple Application - Location Issue and the Application Multi-Location Issue are designed to occur based on the following defaults:

  • If ten or more applications at the same location experience performance issues within a 15-minute window, the Multiple Application - Location Issue is triggered. Performance metrics can include any streamed application data passing through the Analytics pipeline, and don't need to be consistent across the affected applications.

  • If the same application exhibits poor performance at three or more locations within a 15-minute window, the Application Multi-Location Issue is triggered. Performance metrics can include any streamed application data passing through the Analytics pipeline and don't need to be consistent across the affected application-location combinations.

Note: In case of a conflict, the Multiple Application - Location Issue takes precedence over the Application Multi-Location Issue to prioritize potential location problems over individual application issues.

Incident Runbooks

We provide two built-in runbooks to deliver immediate value and offer clear, practical examples. You can clone and customize these runbooks as needed to fit your specific use case. Although we optimized the current configurations for environments that leverage AppResponse, you do not need AppResponse to benefit from this functionality.

Note: When customizing or building a new runbook, the same Triggering Entity can be applied to each application issue. The trigger can return a single application and location, or an array of apps and locations. Technically, a single runbook could respond to all application triggers, but it's best to tailor the runbook to handle specific scenarios.

  • Multi-App Location Issue — Assumes there is a location-wide problem affecting multiple applications and users at a specific site. The runbook captures data on the affected applications, their performance, and the overall location performance.

  • App Multi-Location Issue — Assumes there is an issue with the application or the servers hosting it, impacting users across multiple locations. The runbook captures data about the application and its performance across those locations.

Incident Types

There are additional included filtering capabilities which you can use to find relevant issues based on specified search parameters. These filters are listed under Incident Type.

System Properties

You have flexible options to configure and manage which applications should be correlated, especially when correlation is not appropriate.

  • Multi-Application Location issues are enabled by default and always active. The system property of Application Rollup is specific to Single Application Multi-Location events.

  • On the Custom Properties page, a system-generated property named Application Rollup is available. As indicated in the property description, when set to True (the default), IQ will perform application correlations automatically. If set to False, no correlation will take place.