Chapter 01 HP RUM 9 Intro to RUM

8/10/2019 Chapter 01 HP RUM 9 Intro to RUM

1/19

Real User Monitor 9Essentials

Chapter 01 Introduction to RUM


2/19


3/19

HPs End User Management Approach


4/19

Supporting Key IT Initiatives with EUM

4


5/19

Real User Experience Challenges

Adequate information toprioritize issues

Isolate an issue to one

customer , a segment ofcustomers, a location orentire set of customers

Associate businessimpact with the issue

If a service goes down, doyou know the businessimpact?

Detailed information inorder to resolve

Details of the path the

real user experienceperformed during thetransaction

Details of how the userwas truly experiencingthe application when theissue occurred

Do you have adequateinformation to quicklyresolve a customerexperience issue?

5

Early warning of actualcustomer experience

issues

Allows for a proactive

response

Warning needs to basedon experiences for allusers from all locations allthe time

Do you monitor yourapplication based oncustomer calls?


6/19

End User Monitoring OptionsIndividual or Combined Solutions

SyntheticCheck health when nobody isusing the business service

Check from different points ofpresence

RealGreat for isolation and diagnosticsUnderstand what users really do


7/19

Real User Monitor (RUM)Tracking and Monitoring Actual User Experience

7

All users , from all locations , all the timeWhat the user did , what was returned and timingMonitors http/https and TCP/IP traffic to web/app servers and

other non-web applicationsMeasure business impact to prioritize IT response


8/19

RUM and the Performance & Availability

Lifecycle (PAL)

Monitor andOptimize

ReuseBusinessProcess

Scripts

TestandOptimize

RecordBusinessProcess

Scripts BidirectionalAsset Reuse

TESTING OPERATIONS

New applicationdeployment

Continuousimprovement(Hot packs, fixes etc)

Major upgrades

Reuse Business Processes Scripts/SLAs from Testing in Production

Leverage Real User Information in Pre-Production

Unified Diagnostics

PAL=Performance and Availability Lifecycle


9/19

Why HP End User Management?Where RUM Fits

Customer focused IT aligns with the businessComplete End User Management solution with industryleading active and passive monitoringManage by business-centric prioritiesResolve problems quickly with integrated diagnosticsApplication life cycle support to reduce time to marketfor application changes

9

Improveservicelevels

Managebusinessimpact

Minimizecustomerdowntime

HP End UserManagement


10/19

10

Real User Monitor

Web and TCP traffic monitorSniffer solutionServer side solution

Non-intrusiveGives information about real usersPassive technology no synthetic transactions ordummy accountsOne place deployment, no maintenance of agentsTracking response time and availability of all usersTracking real business processes


11/19

User

WebServersSwitch

Firewall

ApplicationServers

Mainframe/DatabaseLoad Balancer

Internet

MirroredTraffic

Real usermonitoring for all

users, from alllocations, all the

time

Takeaways: Capture the real user experience When active transactions not allowed (ex: finance , ERP) Understand number of users impacted by problems

Real User Monitor (RUM)

Passive Monitoring for all users all the timeReal

User Monitor

Business Availability Center (BSM)End


12/19

12

How RUM Works

HP BSM Servers

HPRUM

Probe


13/19

HTTP(s

13

Internet

BSM DB( MS SQL or

Oracle )

HTTP(s)

JDBC

P

BSM Servers(Win 2K/03)

Target Servers

HTTP(s)

HTTP(s)

Web Users

Switch orLoad Balancer

)

HTTP(s)

Database Server(s)

ODBC

HTTP(S)SSH

RUM Probe

Sessionizes user requests Masks sensitive content in memoryso it is never written to disk The probe listens to requests andresponses sent to and from the server. Local caching in case of networkconnection loss

Engine

Receives the data collected by the probe andassembles this data according to the configuration specifications it receives fromHP Business Service Management


14/19

RUM System Architecture

14

Star topology to reduceWAN traffic and improvePerformanceEncryption for data in transitAdvanced content cachingBuilt in health monitoring

Fault tolerant designImproved security


15/19

15

RUM Basic Concepts Application

Application is a CI, can be a web, SOAP, Request Response,Streaming or Citrix Application. It is a logical definition , you

can have several applications on the same server or severalservers for one application.

Shared between RUM, BPM, Diagnostics and TV. Must be configured and defined to be monitored. We have many templates types predefined.

Action

One or more server request which are a partof one logical action . Actions are defined different in each protocol.

- An HTTP page is an action defined using URL- A SQL query is an action defined using table, schema,

query type.


16/19

16

RUM Basic Concepts Cont.

Transaction Shared between RUM, BPM, Diagnostics and TV. May be defined by BPM or RUM. Single or series of actions that an end user performs in anapplication, whose performance, availability you want to

monitor.

Session Succession of hits from the same End User

According to IP

According to Session ID (Session ID Detection)Two ways to start or end a session:

Reset Page (start or end a session) Timeout (end a session)


17/19

RUM Basic Concepts Cont.

RUM Reports discovered hosts and software Cis to the RTSMAs part of the model. If more than one application is running in the same host , RUMWill report more than one software element for the same host RUM identifies software elements by the ports and protocols .

Servers

Events An action or occurrence triggered by a predefined criteria .An event can be a error event which affects the availability of the page,or an informational event.There are four Event types : HTTP Errors (404, 500 etc)

Informational Events: Text Pattern Event matched in a page Application Errors are Informational or Performance eventsdefined as Errors.

Page Size. End user group/Sub Group End user group is defined by a

range of IPs or by user names which are user accessing themonitored applications.


18/19

Basic Concepts Cont.

Snapshot on Error (SSOE) We can configure RUM to save a snapshot when Error event occur .

Session replay - capture the user sessions and display it in abrowser outside the explorer window with all its details and snapshots (ifan error occurred) we can also download this session and view itoutside BSM (it is not a report ).

PagePages belongs to an applicationDefined inside an application not CI Single page can be define as atranaction .

BCP (Business Critical Page). A page configured in MonitorAdministration to be monitored by RUM.


19/19

RUM Security Concerns

Security Concerns Best practices User confidentiality Legal restraints Separation of duties

Security risks Fraud concerns Sensitive business data National security Audit rules

RUM Controls Access rights

Where can the data go? What gets captured?

Sessions

Snapshots Fields Scope of control

Applications App components Information

Chapter 01 HP RUM 9 Intro to RUM

Documents

Transcript of Chapter 01 HP RUM 9 Intro to RUM