Openbravo Performance Monitoring

Openbravo Performance
© 2014 Openbravo Inc. All Rights Reserved.
Monitoring
November 6, 2014
Graphene (credit: University of Bath)

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

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

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
1.850 EUR 1.850 USD 2.400 USD 1.500 USD

Agenda
2.1 Logical Model
2.2 Business Transactions (BTs)
2.3 Snapshots
2.4 Hardware and JVM statistics
2.5 Time range
5. AppDynamics Demo
6. Q&A
http://wiki.openbravo.com/wiki/AppDynamics_Overview

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
Application
https://docs.appdynamics.com/display/PRO39/Logical+Model

2.1. Logical Model

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
https://docs.appdynamics.com/display/PRO39/Monitor+Business+Transactions

2.2. Business Transactions (BTs)

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
https://docs.appdynamics.com/display/PRO39/Transaction+Snapshots

2.3. Snapshots

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

2.4. Hardware and JVM statistics

2.5. Time range
▪ Defines the period of time the data is shown for
▪ It is applied globally
▪ Custom ranges can be saved
http://wiki.openbravo.com/wiki/AppDynamics_Overview#Global_Time_Range

Agenda
3.1 Continuous Monitoring
3.2 Proactive Monitoring
3.3 Reactive Monitoring
3.4 Comparison after fixes
5. AppDynamics demo
6. Q&A
http://wiki.openbravo.com/wiki/Monitoring_with_AppDynamics

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

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

Agenda
5. AppDynamics demo
6. Q&A
http://wiki.openbravo.com/wiki/Monitoring_with_AppDynamics#Proactively

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)

3.2. Proactive Monitoring

Agenda
5. AppDynamics Demo
6. Q&A

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

3.4. Comparison after fixes
▪ Compare instance performance during two periods of time
• Overall performance comparison
• Per BT comparison
Goal: check how changes affect in real life

3.4. Comparison after fixes

Agenda
4.1 Munin
4.2 Examples
5. AppDynamics Demo
6. Q&A

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

4.2 Examples
Example evolution of Database size over course of a year

4.2. Examples
Server disk space usage to capacity planning:
When system will run out of space with current growth

4.3. Examples
Database connection usage over time
Shows 3 clear problems which did trigger alerts

Agenda
5. AppDynamics Demo
6. Q&A

4. Use case
Continuous monitoring to detect potentially problematic transactions

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

Openbravo Performance Monitoring

Recommandé

Recommandé

Contenu connexe

Similaire à Openbravo Performance Monitoring

Similaire à Openbravo Performance Monitoring (20)

Plus de Openbravo

Plus de Openbravo (20)

Dernier

Dernier (20)

Openbravo Performance Monitoring