Weitere Àhnliche Inhalte
Ăhnlich wie Openbravo Performance Monitoring (20)
KĂŒrzlich hochgeladen (20)
Openbravo Performance Monitoring
- 1. Openbravo Performance
© 2014 Openbravo Inc. All Rights Reserved.
Monitoring
November 6, 2014
Graphene (credit: University of Bath)
- 2. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
3. Application Monitoring with AppDynamics
4. System-level Monitoring with Munin
5. AppDynamics Demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
- 3. 1.1. Openbravo Application Monitoring Tool
âȘ The Openbravo Application Monitoring Tool is a commercial module
based in a third party solution by AppDynamics
âȘ It includes license for AppDynamics and delivers a pre-packaged
configuration to work with Openbravo
âȘ It is installed as any other commercial module. Extra set-up in
Openbravo server is required after installation
âȘ This tool helps to deliver Performance Assurance to Openbravo
customers by allowing you to
âą Monitor Application Performance
âą Alert when there are problems
âą Help to pinpoint root causes
© 2014 Openbravo Inc. All Rights Reserved.
- 4. 1.2. How to acquire it
âȘ The Openbravo Application Monitoring Tool based in AppDynamics is
acquired as a commercial module (Yearly Subscription) for each
Openbravo server (JVM) that requires application monitoring
âȘ Included for free for 1 server for Openbravo Enterprise Edition customers
âȘ Available as an option for Openbravo Professional Edition customers
âȘ Additional units can be acquired to cover additional servers
âȘ A 30% discount is applicable from second unit onwards
Module Zone 1 Zone 2 Zone 3 Zone 4
Openbravo Application Monitoring Tool
based on AppDynamics
© 2014 Openbravo Inc. All Rights Reserved.
1.850 EUR 1.850 USD 2.400 USD 1.500 USD
- 5. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
2.1 Logical Model
2.2 Business Transactions (BTs)
2.3 Snapshots
2.4 Hardware and JVM statistics
2.5 Time range
3. Application Monitoring with AppDynamics
4. System-level Monitoring with Munin
5. AppDynamics Demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/AppDynamics_Overview
- 6. 2.1. Logical Model
âȘ Business Application
âą Models all the components that provide a set of functionality
âȘ Tiers
âą Represents a key functional module, ie. different Openbravo instances
communicating each other
âȘ Nodes
âą Basic processing unit (JVM), ie. in an environment with application server clustering
each of the nodes in the cluster would be a node in AppDynamics Business
Application
Default Openbravo configuration is a single tier with a single node for each Business
© 2014 Openbravo Inc. All Rights Reserved.
Application
https://docs.appdynamics.com/display/PRO39/Logical+Model
- 8. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
2.1 Logical Model
2.2 Business Transactions (BTs)
2.3 Snapshots
2.4 Hardware and JVM statistics
2.5 Time range
3. Application Monitoring with AppDynamics
4. System-level Monitoring with Munin
5. AppDynamics Demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/AppDynamics_Overview
- 9. 2.2. Business Transactions (BTs)
âȘ The mechanism AppDynamics orders and monitors application traffic
âą Represents logical user activity in Openbravo. Such as: queries in a grid, processing
documents, background processes...
âȘ Configurable
âą AppDynamics for Openbravo module provides default configuration with a minimum
set of meaningful BTs
âą BTs detection can be fine tuned as per customer needs
âą Number of BTs is limited to 50
âȘ Allows to see performance metrics for each BT
âą Each BT can define its performance thresholds
© 2014 Openbravo Inc. All Rights Reserved.
https://docs.appdynamics.com/display/PRO39/Monitor+Business+Transactions
- 11. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
2.1 Logical Model
2.2 Business Transactions (BTs)
2.3 Snapshots
2.4 Hardware and JVM statistics
2.5 Time range
3. Application Monitoring with AppDynamics
4. System-level Monitoring with Munin
5. AppDynamics Demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/AppDynamics_Overview
- 12. 2.3. Snapshots
âȘ A set of diagnostic data, taken at certain point in time for an individual
BT
âą It can include executed SQL queries, stack traces, errors, parameter information,
which Openbravo session executed it...
âȘ Not taken for every BT. Some (configurable) rules trigger snapshots:
âą Periodic collection, by default every 10 minutes a snapshot of each BT is recorded
âą Slow, very slow, stalled or error BTs are recorded
âą BT Health Rules violation can trigger a Diagnostic Session
© 2014 Openbravo Inc. All Rights Reserved.
https://docs.appdynamics.com/display/PRO39/Transaction+Snapshots
- 14. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
2.1 Logical Model
2.2 Business Transactions (BTs)
2.3 Snapshots
2.4 Hardware and JVM statistics
2.5 Time range
3. Application Monitoring with AppDynamics
4. System-level Monitoring with Munin
5. AppDynamics Demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/AppDynamics_Overview
- 15. 2.4. Hardware and JVM statistics
âȘ Hardware statistics are collected (if Machine Agent is running)
âą CPU utilization
âą Memory
âą Disk and Network I/O
âȘ JVM information
âą Heap utilization
âą Garbage collections
âȘ This info can be easily accessed from snapshots to understand how HW
and JVM were in that period of time
© 2014 Openbravo Inc. All Rights Reserved.
- 17. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
2.1 Logical Model
2.2 Business Transactions (BTs)
2.3 Snapshots
2.4 Hardware and JVM statistics
2.5 Time range
3. Application Monitoring with AppDynamics
4. System-level Monitoring with Munin
5. AppDynamics Demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/AppDynamics_Overview
- 18. 2.5. Time range
âȘ Defines the period of time the data is shown for
âȘ It is applied globally
âȘ Custom ranges can be saved
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/AppDynamics_Overview#Global_Time_Range
- 19. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
3. Application Monitoring with AppDynamics
3.1 Continuous Monitoring
3.2 Proactive Monitoring
3.3 Reactive Monitoring
3.4 Comparison after fixes
4. System-level Monitoring with Munin
5. AppDynamics demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/Monitoring_with_AppDynamics
- 20. 3.1. Continuous Monitoring
Goal: detect potential problems even before they become a real issue
âȘ Slow transactions
âą Slowest BTs can be easily detected
âą They should be checked because they can become problematic
âȘ Baseline Comparison
âą Baselines defines performance behavior (load, response times and errors) for the
overall application as well as for individual BTs
âą These base lines can be compared with actual behavior during a period of time
âȘ Errors
âą Erroneous transactions are detected and snapshots are taken
© 2014 Openbravo Inc. All Rights Reserved.
- 21. 3.1. Continuous Monitoring
© 2014 Openbravo Inc. All Rights Reserved.
Fine tuning BTs
âȘ BT split
âą Problematic BTs can be splitted to get more granular information. Ex. two
components (URLs) in the same BT, one of them works fine whereas the other one is
slow
âą This split will allow to understand the real impact of the slow part of the BT as well as
to compare its behavior once a fix is applied
âą Split is done by configuring Instrumentation > Custom match rules
âȘ Data collection
âą HTTP parameters can be configured to get additional information in snapshots
âą Done through Instrumentation > Data Collection
âȘ Valuable information for developers in charge of fixing the issue
âą It also indicates if the problem is coming from Openbravo product or from a
customization
- 23. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
3. Application Monitoring with AppDynamics
3.1 Continuous Monitoring
3.2 Proactive Monitoring
3.3 Reactive Monitoring
3.4 Comparison after fixes
4. System-level Monitoring with Munin
5. AppDynamics demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/Monitoring_with_AppDynamics#Proactively
- 24. 3.2. Proactive Monitoring
Goal: get automatic notification as soon as something starts going wrong
âȘ Health Rules
âą Define acceptable performance indicators for BTs or HW
âą Two violation levels: Warning and Critical
âą Automatic monitor of these values
âȘ Notification on Health Rule violation
âą Policies define email notifications for the selected Health Rules when they reach the
desired level (warning or critical)
âą Depending on the Health Rule type recipient might be System Admin (ex. too much
CPU/Heap usage) or Technical staff to understand the problem (ex. slow BT)
© 2014 Openbravo Inc. All Rights Reserved.
- 26. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
3. Application Monitoring with AppDynamics
3.1 Continuous Monitoring
3.2 Proactive Monitoring
3.3 Reactive Monitoring
3.4 Comparison after fixes
4. System-level Monitoring with Munin
5. AppDynamics Demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/Monitoring_with_AppDynamics#Proactively
- 27. 3.3. Reactive Monitoring
Goal: pinpoint problem root causes when the system has poor performance
âȘ Narrow time range down to the period the problem was noticeable
âȘ Follow the same procedures defined for Continuous Monitoring but
focusing on Problematic BTs
© 2014 Openbravo Inc. All Rights Reserved.
- 28. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
3. Application Monitoring with AppDynamics
3.1 Continuous Monitoring
3.2 Proactive Monitoring
3.3 Reactive Monitoring
3.4 Comparison after fixes
4. System-level Monitoring with Munin
5. AppDynamics Demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/Monitoring_with_AppDynamics#Proactively
- 29. 3.4. Comparison after fixes
âȘ Compare instance performance during two periods of time
âą Overall performance comparison
âą Per BT comparison
© 2014 Openbravo Inc. All Rights Reserved.
Goal: check how changes affect in real life
- 31. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
3. Application Monitoring with AppDynamics
4. System-level Monitoring with Munin
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/Monitoring_with_AppDynamics#Proactively
4.1 Munin
4.2 Examples
5. AppDynamics Demo
6. Q&A
- 32. 4.1. Munin
âȘ Another monitoring tool with different focus (System, System
Administrator)
âȘ Complementing AppDynamics with system-level monitoring
âȘ Not only focused on performance
âȘ Extensible with custom metrics (i.e. Concurrent Openbravo Logins over
time)
âȘ Similar features available:
âą Graphing of metrics for 4 time periods (daily, weekly, monthly, year)
âą Alerting for user-defined thresholds
© 2014 Openbravo Inc. All Rights Reserved.
- 33. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
3. Application Monitoring with AppDynamics
4. System-level Monitoring with Munin
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/Monitoring_with_AppDynamics#Proactively
4.1 Munin
4.2 Examples
5. AppDynamics Demo
6. Q&A
- 34. 4.2 Examples
Example evolution of Database size over course of a year
© 2014 Openbravo Inc. All Rights Reserved.
- 35. 4.2. Examples
Server disk space usage to capacity planning:
When system will run out of space with current growth
© 2014 Openbravo Inc. All Rights Reserved.
- 36. 4.3. Examples
Database connection usage over time
Shows 3 clear problems which did trigger alerts
© 2014 Openbravo Inc. All Rights Reserved.
- 37. Agenda
1. Openbravo Application Monitoring Tool
2. AppDynamics Concepts
3. Application Monitoring with AppDynamics
4. System-level Monitoring with Munin
5. AppDynamics Demo
6. Q&A
© 2014 Openbravo Inc. All Rights Reserved.
http://wiki.openbravo.com/wiki/Monitoring_with_AppDynamics#Proactively
- 38. 4. Use case
Continuous monitoring to detect potentially problematic transactions
© 2014 Openbravo Inc. All Rights Reserved.
- 39. Questions & Answers
Thank you very much for your interest!
Additional documentation about AppDynamics can be found here:
https://docs.appdynamics.com
Front page photo: Graphene (Credit: University of Bath)
High-quality graphene is very strong, light, nearly transparent and an excellent conductor of heat and electricity.
Its interactions with other materials and with light and its inherently two-dimensional nature produce unique properties.
Important Notices:
âą This document contains privileged and confidential information prohibited to be distributed without prior Openbravo consent
© 2014 Openbravo Inc. All Rights Reserved.