Table of Content
Servlets
AppDynamics will detect the servlet based business transactions of SAP Hybris out of the box. You can improve the initial configuration by grouping pages for products, categories, or web content.
In the Controller UI, open the Transaction Detection tab in the Configuration Instrumentation configuration page. Scroll down and add custom match rule, with the following settings:
Category Page
- Select the Entry Point Type for this Rule: Servlet
- Name: Category Page
- Enabled: yes
- Background Task: no
- Priority: 0
- Transaction Match Criteria: Enable URI Contains /c/
Product Page
- Select the Entry Point Type for this Rule Servlet
- Name: Product Page
- Enabled: yes
- Background Task: no
- Priority: 0
- Transaction Match Criteria: Enable
- URI Contains /p/
Web Content
Select the Entry Point Type for this Rule: Servlet
- Name: Web Content
- Enabled: yes
- Background Task: no
- Priority: 0
- Transaction Match Criteria: Enable URI Contains /w/
Servlet Page
- Select the Entry Point Type for this Rule: Servlet
- Name: Servlet Page
- Enabled: yes
- Background Task: no
- Priority: 0
- Transaction Match Criteria: Enable URI Contains /s/
CronJobs
To obtain visibility into the CronJobs executed by SAP Hybris, execute the following optional steps.
- Open the Transaction Detection tab in the Configuration Instrumentation configuration page. Scroll down and add custom match rule, with the following settings:
- Select the Entry Point Type for this Rule: POJO
- Name: CronJob
- Enabled: yes
- Background Task: yes
- Matches Class that extends a Super Class that Contains AbstractJobPerformable
- Method Name equals perform
- To identify individual CronJobs as business transactions, open the tab Transaction Splitting and add the following settings:
- Enable "Split Transactions using on of the following mechanisms..."
- Enable "Use a method parameter to name Transactions"
- Parameter Index 0 Getter Chain to run on method parameter getCode()
Web page naming
If you have added the agent for Browser Real-User Monitoring (found in SAP Hybris with AppDynamics - Customization and setup ), all pages will be detected out of the box.
Group product, category, web pages by modifying the configuration.
- Open the Web Page Naming, Error Detection, Thresholds, Percentiles etc. tab in the Configuration page of your User Experience application and add the following Custom Naming Rules within the Configure how Pages, AJAX Requests and iFrames will be named section:
- Category Page
- Name: Category Page
- Enabled: Yes
- Priority: 0
- URL Contains /c/
- Enable Don't use the URL
- Enable Don't use the anchor
- Product Page
- Name Product Page
- Enabled: Yes
- Priority: 0
- URL Contains /p/
- Enable Don't use the URL
- Enable Don't use the anchor
- Web Content
- Name: Web Content
- Enabled: Yes
- Priority: 0
- URL Contains /w/
- Enable Don't use the URL
- Enable Don't use the anchor
- Servlet Page
- Name: Servlet Page
- Enabled: Yes
- Priority: 0
- URL Contains /s/
- Enable Don't use the URL
- Enable Don't use the anchor
JMX monitoring
SAP Hybris provides a lot of insight via JMX metrics.
Open the JMX tab in the Configuration Instrumentation configuration page and import the JMX metric configuration attached to this article. Then create alerts or dashboards based on these additional metrics. More information found here: SAP Hybris and AppDynamics - Dashboards
SOLR monitoring
Out of the box, AppDynamics already detects SOLR as a remote service and provides you with valuable insights like "Calls per Minute" and "Average Response Time."
For deeper insight into SOLR, you have two options: Instrument SOLR with the AppDynamics Java Agent, or add the SOLR extension to your machine agent.
Additional Resources
SAP Hybris with AppDynamics - Customization and setup
