Dynatrace FastPack for Liferay DXP

Transcription

1 Dynatrace FastPack for Liferay DXP

2 The Dynatrace FastPack for Liferay Digital Experience Platform provides a preconfigured Dynatrace profile custom tailored to Liferay DXP environments. This FastPack contains sensors, a template system profile with measures and business transactions, and dashboards for the Liferay platform. If you are using UEM, you will also get conversion and visitor tagging. The focus of the FastPack is page performance in relation to the portlets utilized on a page. FastPack Details Name Liferay DXP FastPack Version 1.0 Dynatrace Version Author License Support Brian Wilson Dynatrace BSD Community Supported FastPack Download contains: Dashboards (see below) Template Profile FastPack Contents Liferay Version FastPack FastPack developed on Liferay DXP: Digital Enterprise 7.0 GA1 Dynatrace Free Trial Download the free 30-day Dynatrace & UEM trial to gain deep user insight, understand application performance across all tiers, identify performance and scalability bottlenecks, and release new code faster. 1

3 Dashboards For more in-depth detail about the measures, business transactions, dashboards, and more in the FastPack, please download the Liferay DXP Profile for Dynatrace Documentation. Liferay Overview There are many aspects to Liferay, so to make performance and problem identification easy we created this high level overview dashboard providing insight into key Liferay services like Blogs, Media Gallery and Search. Context is important, too. Besides viewing the health of page performance, the overview dashboard provides a window into key metrics that may be impacting page performance. These include site load, database activity, thread usage and Ehcache metrics. In addition, the Layer Breakdown provides a view into which classes are consuming the most time, while the Agent Breakdown highlights how much time, and more importantly, what kind of time CPU, Database, Sync, Wait & Suspension is being consumed in each tier. By starting at the Liferay Overview, teams can quickly ascertain the nature of the problem at hand and proceed to diagnosing the problem with only involving the teams needed for the nature of the problem instead of pulling everybody together for an unnecessary war room. 2

4 Liferay [Portlet Type] Overview Most of the Portlets use the Liferay MVC framework as their implementation. Transactions then split on the significant portlet parameter which was used to form the portlet URL. Identifying these pages with a Business Transaction is not only a key to providing alerting in the Overview dashboard, but a key to understanding the performance of the different page types in Liferay DXP. Most portlets can be identified by either Action Processed, Resource Served or View Rendered. What this means is that, for instance, a Wiki page is not simply a Wiki page. By identifying and monitoring portlets by Portlet Phase, a slow Wiki page can be identified to actually be a slow Wiki Action Processed Page. Not only does this narrow down the scope of an issue ( All Wiki pages are slow. vs. Wiki Action pages are slow. ), it immediately provides teams a targeted subset of data to analyze further for root cause analysis. In total, there are six versions of this dashboard, one each for: Asset Publisher, Blog, Documents and Media, Message Boards, Web Content and Wiki. 3

5 Liferay CMS Overview A very large portion of pages served by Liferay will be served by the Liferay Content Management System. Simply identifying that CMS pages are slow or failing is too broad. CMS pages can be Private Site pages, Private User pages or Public pages. Additionally, they can be sub-categorized by portlet phase: action phase, render phase and resource phase. Furthermore, they may be impacted by specific individual portlets of any phase that are present on the page. Ultimately, then, when CMS pages are slow, it s important to know which specific pages are slow and to determine if it s because of a specific portlet on the page or if it s something broader, like a slow query or issues elsewhere in the code. This dashboard brings clarity to this by identifying and analyzing CMS pages along these groups. The CMS Page Overview provides details about performance, throughput and errors across multiple dimensions. It even lets you know if there are any host or process health issues that may be contributing to the slowness. Liferay CMS Page Performance Analysis When there s a problem with specific pages, deeper analysis can be conducted in the CMS Page Performance Analysis dashboard. By selecting a specific page on the top left, users can analyze the page for fault domain, API hotspot and database hotspot errors, as well as identifying which portlets, in their corresponding phases, are on the page and if they are contributing to latency. 4

6 Liferay Search Overview Liferay leverages several search engines to get the job done and it s important to monitor the performance of each. Liferay ships with Elasticsearch or can be configured to use the Solr plugin. Index searcher determines which of these two engines is implemented and delegates the search to the appropriate implementation for that search engine. Faceted search returns documents matching the search. The Liferay FastPack exposes the time spent on each of these and their impact on the actual individual search transactions. In addition, it s important to monitor the overall performance of the Search portlet page by view rendered. Liferay HTTP API Request Analysis This dashboard has the same parent/child relationship as described in the Liferay CMS Page Performance Analysis dashboard, but since portlets are not part of these pages, the portlet tabs are not present. Select any API request split to determine where time is being spent in each page request type. Drill down to PurePaths for a granular view. 5

7 Liferay Worst Performers The Liferay Worst Performers dashboard provides a view of the slowest transactions and more. In the upper half, there s a comparison of tier and package performance comparing the fasted 90th percentile with the slowest 10th percentile. This tells you, overall, where the latency is coming from for the slowest activity on your site. The bottom half contains what we like to think of as an improvement checklist. It includes the slowest web requests, slowest user actions, slowest web services, slowest database queries, top client (browser/device) errors and top application errors. From these lists, the business owners can easily prioritize where to spend time on making improvements to the existing sites. 6

8 Liferay Ehcache Metrics Liferay relies heavily on Ehcache to deliver a fast user experience. This is a good thing. As a general rule of thumb, if something can be cached, it should be. What is not good is ignoring your cache. All too often, developers make the mistake of enabling caching without making sure it s optimized or even being leveraged. The Ehcache dashboard, complete with pre-defined threshold alerts, is designed to provide that awareness of cache usage. Specifically, this dashboard monitors Cache Occupancy Rate in memory and In-Memory Hit percentage for the different Ehcache caches. If page performance slows down, it is very easy to determine if misconfigured Ehcache is contributing to that problem. 7

9 Liferay Process Monitoring Not every problem is related to code. In fact, many problems are simply a result of a poorly tuned JVM. Even with the most finely tuned code and JVM, a host will always have a limit. Common causes of latency in a Liferay system include GC pauses and misconfigured thread pools. The Liferay Process Performance dashboard monitors process CPU health, heap/gc utilization, the impact of GC on response times, and JVM/Liferay Thread pools. These provide great insight in whether or not threads and memory need tuning. Liferay System Monitoring The Liferay System Monitor dashboard adds the context of host performance metrics like host CPU, host memory, disk I/O, and network I/O along with page performance and visit load. Sometimes a problem is as simple as a full disk because somebody misconfigured log clean-up. With an eye on page and visit load, it s simple to determine if the server/process is just simply overloaded with traffic, or if there s a bigger problem with low load. 8

10 Liferay Database Performance In almost any application, database performance still ranks as one of the top performance problems. The teams at Liferay see the same thing in their customer engagements as well. Three of the most common problems on the database side are the N+1 query, slow queries and JDBC pool usage. The Liferay Database Performance Dashboard shines a light on these and other database problems, including database host health. Installation Just download and import the FastPack on your Dynatrace Server (see Plugin Management). Either configure your commerce agents name to start with Tomcat or JBoss_Liferay, as listed in the Tomcat or JBoss agent group, so they will be mapped to the system profile contained in the FastPack, or copy the profile to match your application and modify the contained agent groups and mappings. To use UEM you will need to match your webserver s agent name to start with Apache_Monitoring, as listed in the Apache agent group, or adopt accordingly. Also make sure to enable the UEM and webserver sensor in the agent configuration (disabled by default). For more in-depth detail about the measures, business transactions, dashboards and more in the FastPack, please download the Liferay DXP Profile for Dynatrace Documentation. Contribution Feel free to contribute any changes on Github. 9

11 Liferay makes software that helps companies create digital experiences on web, mobile, and connected devices. Our platform is open source, which makes it more reliable, innovative and secure. We try to leave a positive mark on the world through business and technology. Companies such as Adidas, Carrefour, Cisco Systems, Danone, Fujitsu, Lufthansa Flight Training, Siemens, Société Générale and the United Nations use Liferay. Visit us at Liferay, Inc. All rights reserved