The document outlines the architecture and components for monitoring end user experience using an applications manager, including database and application servers, reverse proxies, and web servers. It details different monitoring methods such as synthetic transaction monitoring, end user monitoring, and website content monitoring to optimize web performance across various geographic locations. Additionally, it highlights the importance of monitoring for website defacement and provides key metrics for assessing web server and services performance.

1. Measure end user experience
using
Applications Manager

2. Web Application
Architecture
Consists of components such as:
• DB servers - SQL, Oracle, etc.
• Application servers - JBoss,
WebLogic
• Reverse proxy - NGiNX
• Web servers - IIS, Apache
• Websites

3. What next?

4. Today's agenda
Synthetic transaction monitoring
Understand user interactions throughout a site
Monitor across geographical locations
Ensure optimal web performance

5. Website monitoring

6. Url Sequence Monitoring
End User Monitoring (EUM)
Website Monitoring

7. HTTP(s) URL Monitor
• Average and Current
Response time
• Response time split-up:
• DNS Time
• Connection time
• First byte time
• Last byte time

8. HTTP(s) URL Sequence Monitor

9. Why URL/ URL Sequence monitor?
• Site is not reachable due to too many people accessing it simultaneously
• Landing page is slow
• Clicking on the page leads to HTTP 500 internal server error
• Some pages lead to HTTP 5012 bad gateway error
Optimizing every URL with received insights for a better user experience

10. Run synthetic end user tests

11. End User Monitor (EUM)

12. Install agents in different locations
(branch offices or customer
locations)

13. Real Browser
Monitoring (RBM)
• Launch a browser and mimic user interactions
with your site.
• Test across geographies.
• Monitored periodically to obtain performance
metrics such as the availability and response
time.
• Use the bundled Firefox browser or import
Selenium IDE test cases to collect metrics.

14. Automatically build monitoring
scripts

15. Monitor multistep user interactions

16. Response times from different
locations

17. Screen capture of the sequence

18. Waterfall graph to identify which element is slowing your
webpage

19. Why do you need an EUM feature?
• Monitor business app performance across geographies
• Measure multipage workflows
• Example: E-commerce, gaming, online banking, etc.
• Test web apps performance
• Test critical pages and paths

20. Website Defacement
Website defacement is an attack on a website that changes the visual appearance of the site or a
webpage. These are typically the work of defacers, who break into a web server and replace the
hosted website with one of their own.

21. Website Content Monitoring
APM standard defacement check includes unauthorized addition or
modification of the following HTML elements:
• Anchor Defacement
• Iframe Defacement
• Link Defacement
• Text Defacement
• Script Defacement
• Image Defacement

22. Web Server and Web Services

23. Web Server/Web Services

24. Web Server/Web Services
Key metrics:
• Request details
• Application pools
• Session Utilization
• Transaction details
• Active connections
• Memory
• Shards count
• Thread pools

25. Quick recap
* Website monitoring using different monitors
• Url monitor
• URL Sequence Monitor
• End User Monitoring (EUM) with Real Browser Monitoring (RBM)
• Website content monitoring
*Web servers/ Web services
*SOAPs and REST API Monitors
Support
appmanager-support@manageengine.com
Eval
eval-apm@manageengine.com
Online Demo
demo.appmanager.com

26. Support
appmanager-support@manageengine.com
Eval
eval-apm@manageengine.com
Online Demo
demo.appmanager.com