Propel_Demo and Propel CAPs

The purpose of the Propel_Demo and Propel Content Acceleration Packs (CAPs) is to provide a set of items (Scorecards, Contexts, KPIs, Metrics, and more) that automatically gathers information from across your enterprise to build key performance indicators (KPIs) related to Propel issues along with OOTB data from the Data Warehouse as well as Dashboard pages that display the relevant information. The CAP includes the Business Application Manager Perspectives. The CAP provides broad and deep insight that should enable you to improve ????Application Availability and improve Application Performance. This CAP provides a 360 degree Propel view.

The Propel_Demo is based on data in .csv files that are part of the CAP package and Propel CAPs include data from data sources.

The relevant content pack is Propel. For details, see Integration with Propel.

ClosedUser Story

Measuring business applications is never easy. IT Organization are facing new challenges when traditional IT moves to the new style of IT.

Chris is the Business Application Manager of the IT organization at ABC Inc. One of his main responsibility is to ensure that all business-related applications are monitored and that their performance is meeting expectations. Chris uses ITBA, a Business Intelligence solution that leverages the analytical functions to help him monitor all business applications and identify the insights in the system to faster resolve the root cause of failures.

  1. During his daily work, he logs into ITBA and opens the Propel Overview Dashboard page to first have an overall view on his measurements.
  2. In the Propel Overview Dashboard page, he checks his predefined Objectives in the Scorecard component.

  3. When he clicks on the Improve Application Availability Objective, the KPI View component shows the Objective KPIs.

    • The Mean Time Between Failures of Applications KPI measures the average expected time between two failures for all the applications during the measurement period.
    • The Percentage of Applications Availability KPI measures the availability rate of the applications during the measurement period.
    • The Percentage of Failed Application Transactions KPI measures the failed rate of application transactions during the measurement period.
    • Additional KPIs show more information about application performance such as Percentage of Applications Meeting 1 Second Performance, Percentage of Applications Meeting 10 Seconds Performance, Percentage of Applications Meeting 1 Minute Performance.
  4. The Metric View component shows the trends regarding the Number of Events, Alerts, Monitored Created Applications, and Average Application Transactions Response Time during the measurement period.
  5. After checking the overall status on Business Application Management, Chris opens the Business Application Performance Dashboard page for further information.
  6. The Business Application Performance Dashboard page is more specific as it measures the result of each KPI in the different layers.
  7. Chris checks the KPI View component, and finds that the statuses of the Percentage of Applications Meeting 10 Seconds Performance and Percentage of Applications Meeting 1 Minute Performance KPIs are red, which means that the applications cannot meet the performance baseline and have big performance issues.
  8. Meanwhile, Chris also finds that the Percentage of Available Applications KPI is also red, which means that the applications only recently became unavailable.
  9. He think that there might be some strong correlations between low application performance and application unavailability.
  10. In addition, in the Historical View component, he sees that the three KPIs trends have been decreasing for the last two weeks, so he decides that the team must return those abnormal states back to normal.
  11. Further, by looking at the Number of Applications by Availability KPI in the Bar Chart View component, he understands that there are currently two unavailable applications.
  12. He suspect that application unavailability might cause the problem. Looking at the Number of Failed Application Transactions by Applications KPI in the Cluster Bar Chart View component, he sees that two cloud-related applications have the top failed times. He decides to send an annotation to Richard, the owner of the Cloud System Application, requesting clarifications: "Richard – We have poor application performance, please provide insight and set a plan by EOW.
  13. When Richard gets the annotation from Chris, he checks his report and starts the analysis of the problem.
  14. Richard then replies to Chris that he will initiate a meeting with the team to address the issue by EOW.

ClosedPropel_Demo and Propel CAPs

????

??? replace ???

User interface elements are described below (when relevant, unlabeled elements are shown in angle brackets):

UI Element

Description
Pages

Propel - Business Application Performance - Dashboard (Demo)

Propel - Overview - Dashboard (Demo)

Scorecards
  • Operations Analytics Demo
  •  
Business Contexts
  • Propel_Demo
  •  

For details, see Semantic Layer - Contexts and Universes.
KPIs and Metrics

Note The Demo CAP includes KPIs with names followed by (Demo). The CAP includes the same KPIs with names that do not include (Demo). The KPIs are the same but have different names so that both the Demo CAP and the CAP can be activated at the same time.

Mean Time Between Failures of Applications KPI. Mean time between failures of applications (MTBF) describes the expected time between two failures for a repairable system. The MTBF calculates the sum of lengths of the application available periods (downtime- uptime) divided by the number of observed application failures.

Percentage of Applications Availability KPI. The number of available applications relative to the total number of applications during the measurement period.

Percentage of Failed Application Transactions KPI. The number of failed application transactions relative to the total number of application transactions during the measurement period.

Percentage of Applications with Performance Through 1 Second KPI. The number of applications with an average performance response time <= 1 second relative to the total number of applications during the measurement period.

>Percentage of Applications with Performance From 1 Through 10 Seconds KPI. The number of applications with an average performance response time > 1 and <= 10 seconds relative to the total number of applications during the measurement period.

Percentage of Applications with Performance From 10 Seconds Through 1 Minute KPI. The number of applications with an average performance response time > 10 seconds and <= 1 minute relative to the total number of applications during the measurement period.

Percentage of Applications with Performance From 1 Minute KPI. The number of applications with an average performance response time > 1 minute relative to the total number of applications during the measurement period.

Average Application Transactions Response Time Metric.The average response time for application transactions during the measurement period.

Number of Events Metric. Number of Events in OpsA during the measurement period

Number of Alerts Metric. Number of Alerts in OpsA during the measurement period

Number of Monitored Applications Metric. The number of applications monitored during the measurement period.

Number of Failed Application Transactions Metric. The number of failed applications transactions that failed during the measurement period.
Data (External Tables)
  • Propel_Alert_Management_Demo
  • Propel_ApplicationPerformanceManagement_Demo
  • Propel_EventManagement_Demo

ClosedPropel - Business Application Performance - Dashboard (Demo)

ClosedPropel - Overview - Dashboard (Demo)

Send Help Center feedback