COMPUWARE Whitepaper Boost Business Agility for IBM WebSphere
Compuware DCRUM Intro 2012 version 12.00
142
Compuware APM - Introduction
description
Some basic information on how Compuware handles agentless, synthetic, Java/.Net monitoring in the consept level, good for getting a basic understanding of the systems and possibilities
Transcript of Compuware DCRUM Intro 2012 version 12.00
Compuware APM - Introduction
Market Trends, Business Challenges & APMThe World is Changing & the Rate of Change is Accelerating
Application visibility and optimization of the customer
experience are more important than ever
Business Demands More Change, Faster
I want change!
I want stability!
Development Operations
Business I want competitive advantage!
Complexity Explosion
User Expectations Continue to Rise
Serv
er
Net
wo
rk
Dat
abas
e
Java
/.N
ET
Web
An
alyt
ics
Sto
rage
Vir
tual
izat
ion
Thir
d P
arti
es
Data Smog and Blind Spots
Market Trends, Business Challenges & APMThe World is Changing & the Rate of Change is Accelerating
Application visibility and optimization of the customer
experience are more important than ever
Business Demands More Change, Faster
I want change!
I want stability!
Development Operations
Business I want competitive advantage!
Complexity Explosion
User Expectations Continue to Rise
Serv
er
Net
wo
rk
Dat
abas
e
Java
/.N
ET
Web
An
alyt
ics
Sto
rage
Vir
tual
izat
ion
Thir
d P
arti
es
Data Smog and Blind Spots
Market Trends, Business Challenges & APMA Case Study for a Changed World
• Akamai x 4
• DoubleClick x 3
• HitBox
• YieldManager
• Google Ad Services
• Atlas Advertising
• Amgdgt.com
• Interlick
• Tribal Fusion
• Turn.com
4 internal content providers
23 external content providers
Verizon CEO Daniel Mead-
“more than 60% of iPhone
sales occurred online.”
That’s 24,000 sales per dayThat’s $5-10m per day
APM in 2010
End User Experience MonitoringCaptures the End User Experience of an application or service
Captures rich statistics regarding components and component domains
Discovers/models application determined logical topology
Traces transaction flow across the IT environment
Consolidated, normalised, correlated & analysed
Application Component Deep Dive
AP
M 2
01
0
Business Transaction Process/Flows
PMDB
Performance Management Database
1.
2.
3.
4.
5.
APM in 2015
APM 2010EUE, deep dive, application model, trans flows, PMDB
Policy setting and workflow orchestration
Understand, analyse application patterns and spot deviations
Distributed knowledge capture, knowledge sharing and improvements
Support cloud model and end to end management – off premises and on
Policy and Orchestration Engine
AP
M 2
01
5
1.
2.
3.
4.
5.
Application Behaviour Learning
Crowdsourcing and Collaboration
Cloud Enablement
Cost Allocation and Chargeback Monitor resource usage6.
Introduction to APM
• Application Performance Management
– End-user
• What is the “end-user” experience?
– Enterprise / Business
• Why Manage End-user Experience?
– Operations
• Typical Enterprise Requirements
• The Application Performance Challenge: Problems Everywhere Along the Delivery Chain
• Traditional Operational monitoring
– Development
• Traditional development flow
• Gartner’s five APM dimensions
• Compuware APM product range
Introduction to APM
End-User: What is the “end-user” experience?
• Application availability and performance for the end-user
• APM for Retail Banking: http://www.youtube.com/watch?v=M7qEuLxQgOM
Button press or request Page Load or response
The Answer: Adopt an Application Point of View That Starts with the User
Application
Customers
Employees
ISPs ▪ Mobile carriers ▪ Browsers ▪ Devices ▪ AJAX ▪ JavaScript ▪ Mobile apps
UsersCloud: Private and Public Data Center Web ▪ Mobile ▪ App logic ▪ Database ▪ Network
▪ Mainframe ▪ Virtualization ▪ SOA ▪ CDNs ▪ Third party services
Infrastructure
Application Point of View that Starts with the End User
Application
• 73% of performance issues are user-reported
– Yet less than 5% actually complain
• End-user Experience impacts business success
– Slow apps reduce revenue by 9% and productivity by 64% *
• Most monitoring is at component level
– Not immediately actionable
• Efficient enterprises accelerate fault domain isolation
– 80+ percent of problem resolution is misspent finding the fault, not fixing it
– Why? Increasing Data Center Complexity
CostREDUCED…
RevenueIMPROVED…
* Aberdeen, “APM: Getting on the C-Level’s agenda
Enterprise / Business: Why manage end-user experience?
Enterprise / Business: Reduce time spent on Awareness and Isolation
Revenue Impact / Cost
Busin
ess Im
pact
IsolateRemediation
Root CauseResolve
Response Times
• Generate alerts and notifications based on configurable transaction thresholds.
• Real Time and Historical performance data specific to app transactions
• Single view of usage, performance and availability for transactions across multiple tiers
• Real-time, detailed diagnostic data specific to users and their transactions.
• Report on business impact and relational diagnosis of faults.
• Enable multiple users at varying levels to consume and use data simultaneously
• Flexible, conditional alerting and reporting.
• Service Level Management and Operational views and workflows minus any extraneous information
• Usage, Performance and Availability monitoring for specific applications and transactions
• Reduce human hours spent isolating and analyzing performance problems
• Efficient communication between IT groups for reactive and proactive initiatives
• Integrate current monitoring investments into a strategic solution for Enterprise development
Operations: Typical Operational Requirements
Application
Customers
Employees
ISPs ▪ Mobile carriers ▪ Browsers ▪ Devices ▪ AJAX ▪ JavaScript ▪ Mobile apps
UsersCloud: Private and Public Data Center Web ▪ Mobile ▪ App logic ▪ Database ▪ Network
▪ Mainframe ▪ Virtualization ▪ SOA ▪ CDNs ▪ Third party services
The Application Delivery Chain
Operations: The Monitoring Challenge: Problems Everywhere Along the Delivery Chain
Infrastructure
• Network peering problems
• Outages
• Inconsistent geo performance• Bad performance under load• Blocking content delivery
• Configuration issues• Oversubscribed POP• Poor routing optimization• Low cache hit rate
• Network peering problems
• Bandwidth throttling
• Inconsistent connectivity
• Poorly performing JavaScript
• Browser/ device incompatibility
• Pages too big• Low cache
hit rate
• Network resource shortage • Faulty content transcoding • SMS routing / latency issues
• Poorly performing Java or .NET methods
• Slow SQL or Web services transactions
• Server performance
• Network problems
• Bandwidth contention
• Improper load balancing
• Resource contention
• Capacity issues• Slow bursting
INTERNETCUSTOMERS
DATA CENTER
Storage DB Servers Web Servers
AppServers
MiddlewareServersMainframe
LoadBalancers
Network
MobileCarriers
ContentDelivery
Networks
MajorISP
LocalISP
Third-party/Cloud Services
Operations: Why Traditional Monitoring Fails
NETWORK TEAM
!
APPLICATION TEAM
SERVER TEAM
MAINFRAME TEAM
This application
is slow!
I’m on it!
DATA CENTER
Storage DB Servers Web Servers
AppServers
MiddlewareServersMainframe
LoadBalancers
Network
NETWORK TEAM
APPLICATION TEAM
SERVER TEAM
MAINFRAME TEAM
INTERNETCUSTOMERS
MobileCarriers
ContentDelivery
Networks
MajorISP
LocalISP
Third-party/Cloud Services
!
Not my Problem!
Not my Problem!
Not my Problem!
Not my Problem! This application
is slow!
Operations: Why Traditional Monitoring Fails
Operations: Why traditional monitoring fails:Datacenter Complexity
Network MonitoringNetscout, Niksun, NetCool, Opnet, Fluke, Cisco Works, EMC Smarts
Load Balancer
Virtualized Web Servers
Firewall
Virtualized Application Server
Load Balancer
Virtualized Application ServersWeb Services, RSA Log File SAN
Message Queue
Database Instance
Application MonitoringWily Introscope, Mercury Topaz , OV Transaction Analyzer, ITCAMs, dynaTrace, Optier, IBM ITCAMs
Component Level Monitoring
Tools
Message Queue MonitoringCandle, BMC Middleware Mgmt, Hyperic, Omegamon
Database MonitoringQuest Software, IBM Tivoli, Quest Fog Light , Precise, Oracle
Server MonitoringPerfmon, Netcool, Sitescope, Solar Winds, Nimsoft, Nagios, MOM
Virtual Env. MonitoringVMWare, Quest vFoglight, Opnet vMon, ZenOS, NetIQ App Manager
Authentication MonitoringImprivata, Zimbra, ActiveIdentity, EMI Security, Juniper J-Web, Juniper
Authentication
App SAN1000 GB
RSA SAN250 GB
Respons
e T
ime
Respons
e T
ime
Respons
e T
ime
Respons
e T
ime
Respons
e T
ime
Respons
e T
ime
Respons
e T
ime
Impossibleto
Correlate &
Troubleshoot
Operations: Why Traditional Monitoring Fails
DATA CENTER
Storage DB Servers Web Servers
AppServers
MiddlewareServersMainframe
LoadBalancers
Network
NETWORK TEAM
APPLICATION TEAM
SERVER TEAM
MAINFRAME TEAM
INTERNETCUSTOMERS
MobileCarriers
ContentDelivery
Networks
MajorISP
LocalISP
Third-party/Cloud Services
!
This application
is slow!
!
All my lights are green!
All my lights are green!
All my lights are green!
All my lights are green! This
application is slow!
CTOService
Manager
War Roomblah blahblah blah
…. !!!!!...……. … ……..
????????
Development: Application lifecycle
Development(local, remote, outsourced)
Test/QA(local, remote, outsourced)
• Load testing
Business
Production(local, remote, outsourced)
• Cloud load testing• Monitoring
✘What?✘Who?✘When?✘How?✘Code?✘Recreate?
✘Business impact?✘Priority?✘Competitive info?
Development: Problems with Application Lifecycle
Too much time reproducing problems!
Not engineered for performance! Too many iterations!
Too many business impacting issues!
Not enough business context!
$$$$$$
Development(local, remote, outsourced)
Test/QA(local, remote, outsourced)
• Load testing
Production(local, remote, outsourced)
• Cloud load testing• Monitoring
Business
All transactions
Click-to-codeAll details
Which users$$ amountConversionsAbandonmentEtc.
Development: Lifecycle-Oriented APM
No need to reproduce issues
Performance from the start
Fewer iterations
24x7, all transactions
Business impact$
Development(local, remote, outsourced)
Test/QA(local, remote, outsourced)
• Load testing
Production(local, remote, outsourced)
• Cloud load testing• Monitoring
Business
Fewer issues
Gartner’s five APM dimensions • Real User Monitoring• Browser, Data Center, Mobile
• Synthetic Monitoring• Backbone, LMile, Private, Streaming, Mobile
1
• Java/.NET• Server• Transaction Trace
• Network• Database
2
• Business Service Manager• 3rd Party Adapters
3
• dynaTrace PurePath4
• Portal and the CAS, ADS• Dashboards• Reports
5
The Compuware APM Solution
INTERNETCUSTOMERS
MobileCarriers
ContentDelivery
Networks
MajorISP
LocalISP
Third-party/Cloud Services
INTERNAL USERSDATA CENTER
Storage DB Servers
App Servers
WebServers
MiddlewareServers
MainframeLoad
Balancers
Network
On-Premises SaaS
Portal Reporting and Dashboards Business Service Management
Data Center RUMEUE and NPM
dynaTraceJava .NET
Last MileRUM
Browser Mobile
MobileStreamin
gBackbon
e
Gomez SaaS multi-tenant data storedynaTrace Enterprise Analysis
InternetEnterprise
Cloud
Private Public
Employees
Mainframe
Storage
Data Center
Web Services
Mobile Components
Web Servers
App Servers
DB Servers
Load Balancers
WANOptimization
Virtual/Physical Environment
Network
LocalISP
Mobile Carrier
Content Delivery Networks
3rd Party/Cloud Services
Browsers
Devices
MajorISP
Customers
Employees
The Compuware APM SolutionOptimize performance across the entire Application Delivery Chain
150+ enterprise-grade nodes
Data centers & cloud providers
Backbone• Monitoring• Load testing
500+ combos of browsers and O/S
5,000+ supported mobile devices
Virtual Test Bed• Cross-browser
testing
150,000+ consumer-grade desktops
168+ countries
2,500+ISPs
Major mobile carriers around the globe
Last Mile• Monitoring• Load testing
• Agentless real user monitoringFirst Mile Real Users
• Real user monitoring
Browsers
Mobile apps
Private agents
Private Last Mile
Enterprise• Application
monitoring
All network segments, servers and
infrastructure
All users
All apps
All trans
Java/.NET analysis
Multi-tier transactions
• Network and server monitoring• Application component analysis• Multi-tier analysis
PurePath
APM Product page: http://www.compuware.com/application-performance-management/
For more information please refer to the support documentation available on http://go.compuware.com
New Product names for version 12
Current Name New Name
Gomez Real User Monitoring – Data Center (aka Vantage Real User Monitoring)
Data Center Real User Monitoring
Gomez Synthetic Monitoring – Private Enterprise (a.k.a. Vantage Active Monitoring)
Synthetic Monitoring
Gomez Business Service Manager (a.k.a., Vantage Service Management)
Business Service Management
Gomez Java and .NET Monitoring (a.k.a., Vantage Java & .NET Monitoring)
Java & .NET Monitoring
Gomez Transaction Trace Analysis (a.k.a. Application Vantage)
Transaction Trace Analysis
Gomez Server Monitoring (a.k.a., ServerVantage)
Server Monitoring
Gomez Network Performance Monitoring (a.k.a., Vantage Network Monitoring)
Network Monitoring
Gomez Mobile Carrier Data Monitoring (a.k.a., Vantage Service Check)
Mobile Carrier
VantageView VantageView (no change)
DCRUM: Driven by End-User ExperienceOptimize performance across the entire Application Delivery Chain
Test/monitor your app the way users access it:What they do: key transactionsWhere they do it: geographic locationsHow they do it: fat clients, browsers and native devices
Prioritize & Resolve Issues:Measure the business impact usersIsolate root causesDeep application and transaction analysis
Deep analysis
Application
All tiers, all transactions, all users
PurePath
Browsers
Mobile apps
DCRUM Capabilities• Agentless real user monitoring• Unifies network and application reporting• Monitors all data center tiers in one dashboard• Optimize EUE for web and non-web• Diagnose root-cause application problems though dynaTrace integration
•Web and non-web applications
•ERP: SAP, Oracle EBS
•Business core: IBM MQ, XML middleware, mainframe front-end
EUE: all users, all transactions
•Whole Application Delivery Chain
•Multi-vendor integration and Multi-tier view
•Network influenced monitoring captures all transactions
End-to-end: whole ADC
•Business impact
•Application-specific decodes (28+)
•All users, all transactions, granularActionable data
•No software agents to deploy or maintain
•Out of Box and bespoke reporting
•Industry’s leading scale for monitoring
Simplicity of deployment
DCRUM Differentiators
DCRUM Monitors All Tiers, Apps and Components
Load Balancer
Virtualized Web Servers
Firewall
Virtualized App Server
Load Balancer
Message Queue
Database Instance
Authentication
Virtualized App ServersWeb Services
InternetWAN
Agentless Monitoring Device (AMD)
Centralized Analysis Server
DCRUM is Optimized for Cisco UCSCompuware has optimized its Gomez APM On-Premises solutions for exclusive delivery on Cisco Unified Computing Standard (UCS) serversUCS is the “gold standard” for delivery of Compuware APM solutions with specialized leasing terms available through Cisco Capital Leasing.
This combination delivers systems
excellence and solution
differentiation providing our
customers with choice and
flexibility to respond to the ever-
changing demands of the business.
Customers can:
- improve application performance
- increase scalability
- simplify operations.
Cisco UCS Servers
&
DCRUM Works With Your EnvironmentApplications
KEY EXAMPLES
Application Infrastructure
KEY EXAMPLES
Process Automation
KEY EXAMPLES
Cloud Services
KEY EXAMPLES
Browsers and Devices
KEY EXAMPLES
+ over 5,000mobile devices
Custom & packaged applications across
multiple tiers
Virtual and physical environments
Existing solutionse.g., Service Desk and Event Management
CDN, Cloud provider, and third
parties
Every commercial browser and mobile
device
1011101010011110101001100001011101
• Multi-tier, multi-vendor data centers increase MTTR
• Simple monitoring does little in complex environments
• Advanced root cause analysis finds these hidden problems
• Data must be collected from all applicationsand devices across all tiers
• Root cause analysis must work to method and code level of apps
Complexity Demands Analytics
• Leading end-to-end application performance analysis across entire application delivery chain
DCRUM: Industry-leading Application Analysis Continued investment in application intelligence Applications
All tiers of the mission-critical applications
360° View of Application Performance Application Health Status for IT Operational Monitoring
Enterprise Operational Dashboard
Current vs. Historical Analysis
Web and Non-Web Applications (e.g. SAP)
Baseline performance and availability with synthetic
Isolated Network Impact on Performance
Isolate the Poorly Performing Data Center Tier
• Existing workflow: 3 levels, multiple choices on each level
The new DCRUM troubleshooting workflow
One report for applications / transactions
Applications transactions
health
One report for all tiers and all
operations
Infrastructure and network drill down
Troubleshooting:
operations, errors, locations, us
er activity
One report for locations and users activity
• New workflow: 3 screens, 3 clicks to the clue
• Out of box reporting provides:
• Enterprise Application Performance view provides up-to-date status on performance, availability, and business impact on your end users as well as a end-to-end view your datacenter infrastructure with 1-click access to trend information.
• Data Center Analysis View provides instant visual indication of problem areas with 1-click access to detailed troubleshooting information.
DCRUM Reporting Dashboards
• Reporting and events in Central Analysis server are linked directly to dynaTraceportal for deep dive diagnostics
DCRUM and dynaTrace integration
• Goal: get to the root cause as quickly as possible
• Approach:
– isolation the problem domain and
– diagnosis of root cause with an integrated solution of bread and depth
dynaTrace: Root Cause in Seconds
From Problem Isolation to Root Cause
End-to-End Transaction Execution Path
• Across tiers: browser –servers - database
• Remoting
• Web Services
• External services
• Code-level depth
• Heterogeneous- .NET & Java
Contextual Transaction Information
• Method arguments
• SQL bind variables
• Synchronization
• Exceptions
• Logs
+ +
Environmental Data• Memory Dumps
• Thread Dumps
• Monitoring data
• PMI, JMX, CLR
• Win, Unix, DB, VMWare, ETC
=
Production DevelopmentTest/QA
Web ServerBrowser / Rich-Client Java .NET Other Database
Synthetics
=dynaTrace
Session
dynaTrace PurePath Provides Deep Dive Diagnostics
dynaTrace Platform Enables Unified Lifecycle Approach to Proactive Performance Management
Test Production
Developers, CI
Automated
Testing,
Tuning,
Diagnostics
Test Centers
Integrate to Automate and Collaborate
Production Edition
dynaTrace 4 – One Platform – Single Product
Test Center EditionDevelopment Team
Edition
Development
24x7 End-to-end
Transaction Tracing,
Monitoring,
Diagnostics
Production, Staging
Staging
Tests,
Tuning,
Diagnostics
IDE, CI, Build Integration
Test Tool Integration
System Management
Automated
Testing &
Continuous
Integration
Performance
Engineering
(Arch Validation,
Profiling)
Application Performance Management
42
Need to increase test frequency and
accuracy?
Automate Performance Analysis
In Test & CI.
Integrate dynaTrace into your build, CI and test
automation environment.
Automate testing –Unit, Load & Functional.
43
How often does the same issue resurface in production release to release? How often
does the same bug reappear?
Automatically detect & Analyze Regressions
Detect performance and reliability regressions
early.
Compare performance and behavior of a current build to previous versions
and baselines.
Automate analysis to enable you to focus on
features instead of debugging.
44
Application not scaling in production
after passing QA?
Assure A Scalable, Performing
Architecture
PurePath Technology® provides true end-to-end tracing -- Browser to Web Server to App.
Server to Database.
Visualize app. behavior under load
for even large, complex applications to prevent scalability issues from reaching
production.
45
What does “fast” or “slow” really mean?
What does “performs well” and “it scales”
really mean?
Meet Performance Goals With KPIs
Measure, track and alert against KPIs --
Service level, Throughput &
Response time.
Compare performance relative to your
competition with SpeedoftheWeb.
46
Debugging applications in the test environment?
Firefighting in production?
Automate Collaboration &
Resolution
Capture issue root-cause when they
occur so engineers simply replay, at code-level, precisely what
happened.
Alerts publish captured PurePath Sessions to issue
tracking systems for engineers to access
immediately.
Gomez SaaSNetwork: The World’s Most Comprehensive Performance and Testing Network
Real-user MonitoringWorldwide, wherever
your users are
High Volume Load Generation6 locations
CloudBackbone Last Mile Virtual Test Bed Your Actual Users
Web Performance Management150+ locations
Web Performance Management and
Load Testing 150,000+ locations
Cross-Browser Testing 500+ browser/
OS combo’s5,000+ supported devices
Gomez SaaS Network: Monitoring the Cloud• Cloud education• Cloud services evaluation
Global Provider ViewCloud Performance Analyzer
Community of cloud-based companies and experts providing:
• Hands-on tools• Best practices
• “Outside in” perspective of cloud service provider performance• Real-time data• Historic comparisons • Performance & availability bottleneck identification
• Independent validation of providers’ SLA claims
Future APM
Compuware Delivers
Provide visibility into the performance of heterogeneous applications from the enterprise to the cloud
Proactive Monitoring
TODAY
Predict application performance issues before they occur
NEAR TERM
Predictive Management
Active Management
Dynamically adjust the infrastructure to prevent application performance problems
NEXT GENERATION
Compuware Concepts
Compuware Concepts
• Information Gathering
• Protocol Analyzers
• Software Services
• Operations, Applications and Transactions
• Reporting Hierarchy
• Tiers
• Locations
• Metrics
Information Gathering
• Application monitoring can only be as good as it is defined.
• Therefore, as much information as possible should be gathered surrounding the to-be-monitored applications:
• Minimally:
– Logical application topology information
– IP address (range) supporting the services for this application
– Port number (range) supporting the services for this application
Information Gathering
End-user Detection coverage
Real User Monitoring
`
Synthetic Auto-check
Synthetic Transaction
Protocol Analyzers
• A.k.a. “decodes”
• monitors, parses, and analyzes a network protocol in the monitored traffic
• Some analyzers perform transaction monitoring: they can recognize exchanges of information where there is a recognizable question-and-answer dialog
• Licensed features
• Examples: TCP, HTTP, HTTPS, XML, MSSQL and Oracle
Software Services
• Services that support an application at different levels, for example on a Web, Application or Database level.
• Are minimally defined by a server IP (range) and a server port (range) together with a protocol, for example:
– HTTP service on server IPs 10.10.10.1-10.10.10.3 on port 80
– SOAP service on server IP 10.10.10.4 on port 8080
– Oracle service on server IP 10.10.10.5 on ports 1521-1523
• Configurable at different levels depending on the underlying protocol:
– Action identification
– Grouping
– Masking
– User identification
Operations, Applications and Transactions
• Logical names / groupings for TCP level actions at different levels.
• Operation:
– Refers to an operation in the context of a particular protocol, and can mean a HTTP/HTTPS page load, database query, JOLT request on a Tuxedo server, DNS look-up etc.
• Transaction (grouping mechanism for operations):
– Simple transaction consisting of a single operation, such as a Web page load.
– Complex transaction consisting of a sequence of operations that are HTTP(S), XML, SAP GUI or Cerner based.
– Unstructured transaction that is a collection of un sequenced operations.
• Application (grouping mechanism for transactions):
– A universal container that can accommodate one or more transactions, which consist of one or more Software Services.
Applications and Transactions
Application 1
Transaction A
Transaction B
Transaction C
Applications and Transactions
Medical Records
Physician Login
Admin Login
Patient Login
URL (http://10.21.79.243/admin/login.do)
URL (http://10.21.79.243/physician/login.do)
URL (http://10.21.79.243/patient/login.do)
Application Performance
Transaction Performance
• Hierarchy levels depend on the analyzer type.
• The CAS can report on up to four levels for the following traffic types:
– HTTP
– SAP GUI
– Cerner
– SOAP
– Any database
• Each level can be reported independently or combined with the remaining ones.
• If you use DMI you are able to create reports with entries from arbitrarily chosen hierarchy levels.
Reporting Hierarchy
• In the current DC RUM release (12) the division to hierarchy levels is supported:
– Operation – The first level in the hierarchy, for example:
URL, Query, SOAP Operation type
– Task – The second level in the hierarchy, for example:
Page name, Operation name, SOAP Method
– Module – The third level in the hierarchy, for example:
Database name, SOAP Service
– Service – The highest level in the hierarchy, for example:
SAP GUI business process
Reporting Hierarchy
Reporting Hierarchy
Reporting Hierarchy
• Start by monitoring the initial entry point of the End-User’s transaction
• Add additional tiers for greater Fault Domain Isolation and Visibility
• Wide variety of transaction support: HTTP/S, Oracle/SQL/DB2/ Queries, SAPGUI, Oracle Forms, XML, MQ
End-Users-Internal?-External?-Internet?
Web Servers Application Servers Database Servers
Mainframe /Other Tiers
Users
CIOCTO
IT MgtData Center Ops
Monitoring TeamApplication Owners
Load Balancers /Content Switches
AMD
CAS and ADSReport Server
Synthetic End-User Transactions
(At Key Locations)
Real User Monitoring - Tiers
Tiers
• A tier is a specific layer where DC RUM collects performance data. Tiers are either pre-defined, or defined by the user in the Central Analysis Server (CAS).
• Immediately after the CAS is deployed, data is reported based on the default tier configuration. If the default tier configuration does not fit your network architecture, you should configure tiers to match your topology
• Tiers are configured globally. You should not create separate tiers for individual applications
Front-end Tiers
• Best practice mark the tier as front-end which is closest to the user or to a device that acts on behalf of the user. In short the first layer the user connects with.
1st tier for example load balancer or Web Server
1st tier after Citrix or Terminal Service
Network Tiers
• Client Network:
Wide Area Network (WAN) from remote sites.
Manually and automatically defined sites (AS and CIDR blocks), except the “All other” site
• Network:
Datacenter Local Area Network (LAN).
“All other” site
Data Center Tiers
DC RUM defined
• Tiers that represent measurements originating from RUM DC and based on different analyzer types are listed in the Data center tiers section:
– Website
– Oracle Forms
– SAP GUI
– Exchange
– Middleware
– Message Queue
– Database
– Datacenter Infrastructure
– FIX
User Defined
• Tiers that are based on software service definitions are listed in the Data center tiers with no rules assigned to them:
– VIP
– Load balancer
– Web servers
– Application servers
– Business logic
– Database servers
Locations
• DC RUM refers to locations as “Sites” and defines them as IP address ranges.
• Location definitions can be made in a three-level architecture in DC RUM :
– Site: lowest level of granularity
– Area: Consists of one or more sites
– Region: Consists of one or more areas
– Availability - The percentage number of successful attempts, that is, the total number of attempts minus the number of failures, divided by the total number of attempts and multiplied by 100%.
– Connection Establishment Timeouts – Number of TCP errors of category 'Connection establishment timeout errors'. This category of errors applies when there was no Connection establishment timeout errors response from the server to the SYN packet(s) transmitted by the client.
– Connection Refused Errors – Number of TCP errors of category 'Connection refused errors'. This category of errors applies when the server rejects a request from the client to open a TCP session. Such a situation usually happens when the server runs out of resources, either due to operating system kernel configuration or lack of memory.
– Server Session Terminations – The number of Server Session Termination errors. This category of errors applies when the server detects an error on the application level and closes the TCP session with a RESET packet.
– Server not Responding – The number of Server Not Responding errors. This category of errors applies when the client closes the TCP session with a RESET packet after the server has failed to respond for too long.
– Idle Sessions - The number of idle TCP sessions, that have not been active for a period of time longer than a predefined time-out time, 5 minutes by default.
Metrics: TCP Availability
– HTTP Availability - The percentage of successful HTTP hits, calculated based on the following formula:
100 * (Hits - HTTP errors) / Hits
All HTTP errors are taken into account.
– HTTP Client Errors - The number of observed HTTP client errors (4xx)
– HTTP Not Found Errors - The number of observed HTTP 404 Not found errors
– HTTP Other Client Errors - The number of observed HTTP client errors other than 401, 404 and 407
– HTTP Unauthorized Errors - The number of observed HTTP 401 Unauthorized errors
– HTTP Server Errors - The number of observed HTTP server errors (5xx)
Metrics: HTTP Availability
– Client ACK RTT - is the time it takes for an ACK packet to travel from the user to the AMD and back again.
– Client RTT - is the time it takes for a SYN packet to travel from the user to the AMD and back again.
– Client loss rate (to server)-The percentage of total packets sent by a client that were lost between the server and the AMD - and needed to be retransmitted.
– Server loss rate (to client)- The percentage of total packets sent by a server that were lost - between the AMD and the client - and needed to be retransmitted.
– Server realized bandwidth - Server realized bandwidth refers to the actual transfer rate of server data when the transfer attempt occurred, and takes into account factors such as loss rate (retransmissions). Thus, it is the size of an actual transfer divided by the transfer time.
– Request time - The time it took the client to send the HTTP request to the server (for example, by means of an HTTP GET or HTTP POST). Note: This time includes TCP connection setup time and SSL session setup time (if any). It starts when the client starts the TCP session on the server and ends when the server receives the whole request.
– Delay - Data transfer delay on a Data Center device, such as load balancer or firewall.
Metrics: Network Performance
Metrics: Round Trip Time RTT
– Application Performance – For transactional protocols, this is the percentage of application transactions completed in a time shorter than the performance threshold. For generic TCP protocols, this is the percentage of monitoring intervals in which user wait per kB of data was shorter than the threshold value.
– Operation Time – The time it took to complete an operation. The term "operation" refers to an operation in the context of a particular protocol, and can mean HTTP/HTTPS page loads, database queries, XML (transactional services) operations, Jolt transactions on a Tuxedo server, e-mails, DNS requests, Oracle Forms submissions, MQ operations, VoIP calls, MS Exchange operations, or SAP operations. Note that an operation can be split over several packets. For HTTP and HTTPS, operation time is the page load time, which is equal to the redirect time plus the network time plus server HTTP time plus server think time.
– Person-hours lost (Performance, Errors, Availability) - In Central Analysis Server, the total monitoring time clients waited for pages to load due to bad service availability and bad application performanceIn Advanced Diagnostics Server, the total time clients waited for pages to load due to bad software service performance, that is, the total monitoring time during which page load time exceeded the predefined threshold. Note that this is not a sum of whole monitoring intervals, but only those intervals' portions during which problems occurred. This metric is not calculated in PVU mode.
Metrics: Application Performance
Metrics: Operation Time
– Zero window size events - Client sets this in TCP header when it wants the other side to slow down with data transmission because it cannot keep up with the transmission speed. Indicates that receiving machine is busy with other tasks.
– Network time - The time the network (between the user and the server) takes to deliver requests to the server and to deliver page information back to the user. In other words, network time is the portion of the overall time that is due to the delivery time on the network.
– Redirect time - The average amount of time that was spent between the time when a user went to a particular URL and the time this user was redirected to another URL and issued a request to that new URL. The difference between Redirect Time and HTTP Redirect Time is that the former counts all operations, while the latter refers only to those operations for which redirection actually took place.
– Server Time – The time it took the server to produce a response to a given request.
– Server operation size - The size of a server operation. In HTTP and HTTPS (decrypted and non-decrypted), server operation size equals the page size.
Metrics: Application Performance
Components and Relations
DCRUM Components
Central Analysis Server (CAS)
Business Service Manager
Service Model
3rd-party Integration
Service Management
Synthetic Monitoring
Performance Management Database
dynaTrace DTM
Agentless Monitoring
Device(AMD)
RUM configuration
Console
Enterprise Portal
Dashboards Operational reports
Data Mining Interface (DMI)
Configuration database
Central Security Server
LDAP, users DB
DCRUM Components - Enterprise portal
• Role of the Enterprise portal
– Adds new report workflow: AHS, DCA
– Optional component
• CAS reports remain as before
– Portal workflow drills down to CAS reports for details
– Seamless from the user perspective
ADS
CAS
AMD
Enterprise Portal
• Central Analysis Server (CAS)
– The main reporting component for dynaTrace Data Center Real-User Monitoring
– Combines measurements from the Agentless Monitoring Device (AMD) using different contexts
– CAS pulls its data from the AMD’s in the form of zdata sample files
– Stores its results in an MS SQL Server database
– Results can be viewed real time or historically
• Agentless Monitoring Device (AMD)
– Network probes that analyze network traffic
• Console Client
– Used for configuring devices and application monitoring
• Console Server
– Stores the configuration in a flat file database
DCRUM Components
• Compuware Security Server (CSS)
– New in the 12.0 release is a new functionality called the Compuware Security Server.
– Provides a central authentication and user management capability for
o Central Analysis Server, Console, Advanced diagnostic server, Enterprise Portal and BSM
– This central component allows Users to defined locally in a CSS database or for the customer to use their own corporate user management system – such as the LDAP based systems Active Directory or Apache DS.
• Advanced Diagnostics Server (ADS)
– Is a separate report server, that is integrated with CAS on reporting and configuration level
– Provides a more detailed, troubleshooting-oriented analysis (i.e. element level for HTTP instead of page level on CAS)
– Supports applications based on HTTP(S), XML over HTTP(S)/MQ, SAPGUI, DB2, MSSQL, Sybase, Informix, Oracle and Oracle Forms
DCRUM Components
– ADS pulls its data from the AMD’s in the form of vdata sample files
– Stores its results in an MS SQL Server database
– Results can be viewed real time or historically
• Enterprise Portal (EP)
– Helps speed the isolation of the fault domain and reduces the cost of troubleshooting issues, while restoring service as quickly as possible.
– Contains robust data mining and report building tools for creating new and customized reports quickly and easily.
– Contains dashboards which display graphs, geographic views, and tabular data regarding service and application quality, fault domain isolation, business impact, and infrastructure health.
– Consolidates reporting, security, and configuration functionality into a single component.
DCRUM Components
Analysis Modules
Transaction decode (analysis modules) include:
• HTTP/HTTPS
• SAP
• SOAP/XML
• Databases: MS SQL, Oracle, DB2, Sybase, Informix
• Oracle Forms
• IBM MQ
• MS Exchange
• Thin Client (Citrix/Terminal Services)
Analysers
Collection
and
Measurement
Information
Database
Analysis
and
Reporting
Central Analysis
Server
AMD
Passive traffic analysis
CAS (Web) Analysis ModulesADS
Advanced Diagnostics
Server
Multi-purpose and Expandable Product Family
CAS (Ent)
HT
TP
(S)
SQ
L\D
B
DN
S
SO
AP
Ora
cle
EB
S
Fau
lt Is
ola
tio
n
Deta
ile
d H
TT
P
Bu
s T
ran
s
Ora
cle
Fo
rms
XM
L
Tu
xe
do
/JO
LT
Cit
rix
Sie
bel
TC
P/I
P
MQ
Network Vantage Probe
Passive traffic analysis
(since v 10.1)
Flow Collector
Netflow data analysis
(since v 10.2)
87
SA
P G
UI
MS
Ex
ch
an
ge
SM
TP
Enterprise PortalDashboards
1
2
3
4
5
1. Real-time and historical trending views of application , user, network and overall data center performance2. Supports web and non-web applications such as SAP.3. Quickly identify poorly performing data center tiers.4. Isolate network performance impact on applications and users.5. Monitor baseline performance and availability with synthetic monitoring.
Industry-leading breadth of analysis
• View overall status of applications and end-user performance through a single dashboard that includes quick drill down views into performance, availability, operation time and usage for individual applications and users.
Optimize end-user experience
Multi-tier Data Center Monitoring
• Caption: Drill down from Application Health Status for a focused analysis of performance by data center tier. Isolating application performance problems in multi-tier environments in today’s modern application and data center architectures is a daunting task for IT, yet the business demands rapid problem isolation to reduce business impact. The new Data Center Analysis View provides instant visual indication of problem areas with 1-click access to detailed troubleshooting information. Isolate tier, server, time period, slow web pages, middleware messages, and database queries in a single interactive view that accelerates fault domain isolation.
Multi-tier Data Center Monitoring (cont’d)
1. Data Center Analysis provides real-time views of application performance, operations, availability and usage along with requests broken down by the supporting tier of infrastructure.
2. Historic detail of performance of tiers is displayed with mouse-over detail of how user and application performance is affected by the corresponding infrastructure tier.
3. Individual application operations are displayed in context of overall application performance, network health and end-user experience.
4. End-user performance is displayed for any infrastructure tier and can be sorted by user group, individual users or client types.
12
3 4
One click to deep-dive application analysis1
2
3
1. DCRUM provides a broad view across infrastructure to triage performance of services, servers operations and websites.
2. Reports on affected users, transaction times and availability quickly surface hot spots in application performance.
3. From DCRUM dashboards, a direct drill down into dynaTrace reporting provides method call and code-level analysis of application performance issues.
Optimize end-user experience (cont’d)
1. Drill down from ‘affected users’ heat map to view individual user performance
2. Identify the application(s) responsible for poor end-user performance.3. For specific users, identify the offending application operation with a
breakdown of slow, fast and aborted requests
1
2 3
Central Security Server
CSS Consolidated User Management• The Compuware Security Server (CSS) is a new consolidated authentication and
user management system in 12.0
ADS
Enterprise Portal
CAS
Local definedusers
Corporate LDAPActive Directory
Apache DS
BSM
CSS
RUM Console
CSS Features / Value• Users have one account/password to access DC RUM and BSM
• Seamless pass-through from Enterprise Portal to CAS / ADS
• Enterprise Portal connects to 12.0 CAS / BSM without login
• Administrator usernames / passwords: One vs. three
• Manage users in one location
• Common roles across components
• Audit logging – online and exportable
• Consistent LDAP and LDAPS access
• Consistent password policies
Central Analysis Server
Central Analysis Server (CAS) – Report Server
• CAS is the main report server and repository for real user monitoring
• Metrics are aggregated at “interval level” for each unique client + operation + server
o An “operation” is a web page load, database query, web service call, etc.
• Other features of the CAS
o Custom reporting (DMI)
o Alerts
o Baselines
• CAS has two personalities.
• Transactional Monitoring (web analysis)
o Focused on specific applications: web, SQL, SOAP, etc.
o NOTE: Not just Web analysis
• Enterprise Monitoring
o General network traffic monitoring
• CAS can also store/report on metrics from synthetic transactions and J2EE & .NET agents
CAS - Data Mining Interface (DMI)
• The DMI is the custom reporting tool for DC RUM
• No need to write custom SQL queries
• 100% web based
• Create reports (tabular, charts) from any DC RUM data source: real user monitoring metrics, Java & .NET agent metrics, etc.
• Reports can be scheduled (send daily summary reports by email every night)
• Reports can be linked together to create a customized drilldown workflow
• Data can be exported
• Report definitions can be imported/exported (for reuse at another client)
• Metric names can be aliased to match customer terminology
• Intimidating to use at first glance, but it’s easy to master
CAS - Data Mining Interface (DMI)
CAS - Data Mining Interface (DMI)
CAS - Alarm System Overview
• The alarm mechanism enables you to be proactive rather than reactive
– Fixed thresholds V Baselines
• Alarms can be sent to a specified e-mail address, or can be sent via an SNMP trap.
– There are also alarms that are generated even if they have no subscribers assigned. Such alarm notifications are recorded in the alarm logs, which store records of all alarms generated.
• Modify the existing alarm or define new alarms.
CAS - Types of Alarms• Alarms based on SQL detectors
– Using SQL queries, these alarms perform queries on the traffic monitoring database. The benefit of using these alarms is that there are no constraints to the complexity of the queries and any event that can be expressed as an SQL query can be detected.
• Alarms based on Java/.NET Monitoring measurements
– VAMETRIC_ALM - for alarms performing queries on measurements related to entry points
– VAMETHODMETRIC_ALM - for alarms performing queries on measurements related to object methods or SQL queries
– PAT_VIO_4_AS_RES - for alarms performing queries on measurements related to JMX/WMI metrics
• Metric alarms
– These alarms provide a simple and fast mechanism for performing complex queries on a set of pre-defined metrics. The advantage of using these alarms is easy of use and modification as well as performance. To define metric alarms, you do not need to know the structure of the database or how to program in SQL. However, not all conditions can be expressed as metric alarms.
• Network alarms
– These alarms are similar in design and function to the metric alarms above, though they view the monitor traffic as it is done on the Network View report.
• Link alarms
– These are fast-executing alarms designed to monitor link utilization as presented on the Link View report.
• Other alarms
– A few other alarms are available which were designed for very specific purposes and which can be modified in only limited ways and which do not allow user access to the detector code.
RUM Console
Components
RUM Console consists of two components:
• RUM Console Server
A back-end server application that maintains configuration images and device information, runs tasks related to configuration management, and provides a Web services API for RUM Console to manage configurations. The server is a Windows-based service that can be installed on a machine with Windows 2003 Server or Windows 2008 Server R2 with a network connection to all of the managed devices within the Compuware APM infrastructure.
• RUM Console
A GUI application for configuring report servers and data collectors. With the console, you can create and edit configurations for Compuware APM devices and propagate such configurations to other Compuware APM devices
RUM Console
• Guided configuration: first time users, easy configuration
– first steps
– Wizard configuration
– Tracing ability
• Entire configuration: experienced user
– All same options
– Health reports
– Sequence transactions
Guided Configuration
Device information
Agentless Monitoring Device
The Agentless Monitoring Device (AMD) is a completely passive device, placing no additional load on the network. The AMD can be connected to the network in two ways:
Spanning the switch
• In today’s switched environments most switches have the ability to mirror multiple ports and or multiple VLAN’s to a single monitoring port. This gives the AMD the ability to passively monitor traffic from a number of different perspectives. Therefore the AMD can see traffic in front of and behind load balancers, as well as all the tiers in between. In cases where the switch can not accommodate more spans, the use of regeneration taps can be favourable. Cisco switches may also use VLAN Access Lists (VACLs) to bridge routed traffic to an outgoing port much in the same way as port mirroring.
Passive Taps
• In certain cases, the use of span ports may not be viable. In this case passive taps may be utilized to capture the application traffic to be monitored. This method requires multiple tap points to fully see all tiers within the application.
AMD
• AMD’s job is to sniff traffic for the purpose of performance monitoring• AMD processes performs initial processing of the data.
• Data is organized into files to be retrieved by report servers at configured time intervals
• Red Hat Enterprise Linux 5+ and 6+• Hardware slots are filled with additional network interface for monitoring
• Monitoring NICs are passive• Can be copper or fiber or mixed
• SSL decryption is performed on the AMD• RSA private key needed• SSL decryption card (Nitrox Cryptoswift)
• Decryption processing is offloaded from main CPU• RSA keys are guarded. They are not stored on disk or in main memory.
• Software only – OpenSSL• AMD does not store/keep packet traces.
• It inspects packets to see the URL, the userid, etc.• The exception is HTTP Header request/response and POST data when using
the ADS report server (optional)• Sensitive data can be masked
AMD
Advanced Diagnostic Server
Advanced Diagnostics Server (ADS) – Report Server
• ADS is the deep-dive report server and repository for real user monitoring on web and SQL applications
• Operations are not aggregated (like in CAS). Every monitored transactions can be reviewed in detail
• Breaks down the page load time by individual web page element (images, css, javascript, etc.)
• Can be used to drill into the transaction to see the input submitted by the user (POST’ed data).
• Supports monitoring of “business transactions”
• Stores data only 3-4 business days
ADS – Report Server Example
ADS – Report Server Example
ADS – Report Server Example
ADS – Report Server Example
Component Scaling
• Incorrect Product Positioning
• Deep-dive bottom-up troubleshooting approach instead of top-down Application Performance and EUE Monitoring
• Using short-term POV parameters in longer term Post-Sales implementation
• All-Traffic without any filters limiting IP addresses
• Too many individual Clients
• No user aggregation
• User ID recognition generates too many identifiers
• “Monitor specific page” defines URL parameter with too many values (such as phone number, etc.)
• Too many regular expressions
• HTTP Application Error tracking in high-end environment
• Storage period is too long without justification
• ADS in high-traffic trying to handle same page volume as VAS
• Setting Unrealistic Expectations with the Customer
What causes sizing problems
• When to integrate multiple report servers?
– When one Central Analysis Server is not enough to store all monitoring data from all Agentless Monitoring Devices.
– When AMDs are geographically dispersed (for example, in different data centers).
– When you need to use Advanced Diagnostics Servers to broaden your monitoring perspective and add in-depth vision alongside CAS reports.
– When you need failover and backup operations to provide high availability of reports.
– When you want all of the reporting in one place.
Report Server Integration and AggregationRECOMMENDED ARCHITECTURES
Scalability: HTTP decode multi-threading
Scalability
• Each version brings more optimal traffic decoding, the version 12 numbers are bit better than 11.7 version again
RECOMMENDED ARCHITECTURES
0
200
400
600
800
1000
1200
1400
1600
11.1 32-bit 11.7 64-bit 11.7 64-bit
multi-threading
32 GB RAM
11.7 64-bit
multi-threading
64 GB RAM
Heavy HTTP analysis: traffic analyzed by the AMD (Mbps) *
* - all HTTP analysis feature are enabled, user recognition and operation recognition uses process-intensive regular
Monitoring Component Capacity Guidelines
• The CAS database should not contain more than 2 million sessions.
• ADS offers two modes:
– Small Website: “Per hit mode” can handle 3M page loads (approximately 10M hits) per day.
– Large Website: “Per page mode” can handle 13M page loads per day.
• For the AMD it differs per traffic profile. Below a few examples can be seen:
123
Distributed data storage benefit
• Reduce number of users maintained in the SQL database
– This reduces number of CAS sessions
– Note: CAS client location structure must be well-defined
• Practical data reduction levels will vary
• Theoretical benefit:• 3x – 7x
reduction in number of sessions
Central Analysis Server - Scalability
AMD scaling
126
RECOMMENDED ARCHITECTURES
AMD AMDAMD
SPAN
Tap
• Passive in-line tap or splitter
– AMD in load-balancing mode
• Intelligent switch (e.g. Gigamon, Anue)
– Each AMD analyzes one or part of one application
CAS scaling
127
RECOMMENDED ARCHITECTURES
• Add more CAS servers and distribute data per monitored Server IP
• Designate one CAS as master
• All DMI reports will use all servers as data source
AMD
CASCASCAS
DCRUM Components - CAS master/slave
CAS, ADS network of master and slaves is seen as ONE by the portal
ADS
CAS
AMD
Enterprise Portal
CAS
CAS master-slave network • One of the CASes is
designated as the master
– Monitoring functionality of this CAS is similar to all other CASEes
– Meta-data for consolidated reports is served from slave servers to the master
– Master builds a consolidated report for the user
• ADS always acts as a slave server
• There are no performance reasons to set up a separate Master CAS
– Just designate one of the CASes in the cluster
CentralAnalysisServer
CentralAnalysis
Server
DMI front-end
CentralAnalysisServer
AMD
Probe
AMD
Probe
AMD
Probe
DMI back-end DMI back-end
DMI back-end
Enterprise Portal
CAS scaling – SQL offload
130
RECOMMENDED ARCHITECTURES
AMD
• SQL database on separate hardware
• Makes sense only if I/O of the SQL server is faster then I/O of the CAS h/w
• Shared SQL servers not recommended for high loads
ADSCASCAS
SQL
Additional Analysis tools
Complex application and network interaction can demand more than real-time monitoring. DCRUM includes a Transaction Trace feature that provides deep root cause analysis needed to quickly remedy complex network problems
Transaction Trace Analysis
1
2
3
Transaction Trace Analysis
1. Dig deeper into server processing delays with Thread Analysis visibility into popular protocols such as HTTP/S, SQL, SAP, WebSphereMQ, RMI/IIOP, CIFS, and more2. Pinpoint the source of application performance problems by identifying the impact of the network on transaction response time3. Roll out applications that perform well from the start by predicting and tuning response time before deployment
Other decodes including Citrix WAN Opimisation
134
Monitoring Citrix
• VTCAM software is installed on presentation server (Citrix or MS Terminal Server)
– Runs a Windows service
– Collects CPU & Memory utilization stats of Citrix host
– Maps back-end application traffic to the responsible end-user (session mapping data)
CASGomez User
CAS reports
Monitoring Citrix
Other
Applications
AMD
Corporate
Network
CAS + Enterprise Analysis
TCP level analysis
Appropriate Analysis Modules
TCAM
Database Servers
Citrix Server Farm
Citrix Remote Users
Web Applications
Thin Client Analysis Module (TCAM)
• TCAM – Vantage Thin Client Analysis Module
• Target Environments
– Citrix and WTS enabled applications
• Deployment Considerations
– A lightweight component is placed on the server to correlate user logins and
back end Citrix conversations.
– The agent uses Citrix API and Microsoft Windows API to obtain information on
which user is opening which TCP sessions from the Citrix/WTS server.
– Agent communicates in real-time with AMD and provides mappings from TCP
session IDs to Citrix user login names. This information is used by AMD to tag
measurements taken on the Citrix<->application server path with actual user
login names.
Thin Client Analysis Module (TCAM)
• Target Environments
– Citrix and WTS enabled applications
• Deployment Considerations
– Additional information on resources utilization (CPU, HDD, RAM, TCP, Number
of Terminal Services sessions and Number of active Terminal Services sessions)
statistics of Citrix server is also available.
– One AMD can monitor multiple Citrix/WTS machines (different
servers, different protocols)
– One CAS can gather data from multiple AMDs and provide a single view of
service delivery
Monitoring Citrix
Monitoring Citrix
Monitoring WAN Optimization
• WAN Optimization Controllers (WOCs) are installed at branch office and data center locations
• The AMD adds a SPAN or TAP on the optimized side of the data center WOC
Monitoring WAN Optimization
