DX Operational Observability

 View Only

BPA-Demo System - Configuring the EUM - Business Payload Analyzer (BPA) and tune the App eXperience Analytics (AXA)

By Jorg Mertin posted Oct 08, 2026 09:53 AM

  

Business Payload Analyzer (BPA) Configuration step by step

 
In your DXO2 tenant, go to Settings and search for eum - select Web Payload Capture Rules(WebServer).   
Note: In this location you can also download the BPA WebServer Plugin and the BTListener
 
If you have enabled the docker or k8s traffic generator, and configured the APMIA_HOST_NAME variable, you should see "APMIA_HOST_NAME-root" existing in the left-most drop down "Select an application" list. If you have not set the APMIA_HOST_NAME, it defaults to BPA-DEMO-DOCKER|K8S (Docker/K8S depending on what you deployed it on).
Make sure the identifying attribute is: REQ_URL_PATH - this is what DX O2 metric path works best.
You select it by scrolling in the "Disregarded Attributes / Attributes that are not captured" field, select the identifying line, and tag is as Identifier by selecting: Reassign as ID top right of thee field.
 
Note: The identifier should be as precise as possible. The BPA-Demo app has a header-variable called X-Page-Id. It will show the exact
unique page you are on. The APM suite however is "optimized" for metric-paths in its display and processing, so we have to adapt to the metric path for now.
 
Make sure this identifier is unique. You can combine it with other attributes that will show up in the DxC tree. Note however that processing these later on will require regular expressions. So for this exercise, we'll stick to the simple metric path approach.
 

Attributes to be captured

Add all the attributes you deem important to be captured. The idea is to add everything that would help troubleshooting an issue.   
For this, we can add everything in relation for a good application execution like statuscode, statusmessage, user agent.   
For our use-cases, make sure you include the following into the Captured Attributes field:
  • RSP_HEADER_X_USER_ROLE: This shows if we're logged in as a user, admin or are anonymous.
  • RSP_HEADER_X_BASKET_TOTAL: This shows the basket total (used for a use case).
  • RSP_HEADER_X_PAGE_ID: This is the real page unique identifier. It helps identify where we really were.
  • RESP_HEADER_X_USE_CASE: This shows if we have logged in as a user triggering a use-case.
  • REQ_HEADER_SEC_CH_UA_PLATFORM: identify the platform we come from: Windows, linux, android, ios etc.
  • SP_HEADER_X_USE_CASE: This shows if we have logged in as a user triggering a use-case (Helper for this demo).
  • RESP_HEADER_X_ALERT: Shows if the locked user use-case has been triggered (Helper for this demo).
 

Basket Total - convert data into a metric

We want to also capture a special field - the basket total.
Currently, the metrics tree can handle integers only (not float), so we have to change the capture value to integer for DXO2 to handle these. This will enable use to configure an alert whenever the basket is empty at check-out.   
 
Follow the bellow steps to configure it:
  1. Select RESP_HEADER_X_BASKET_TOTAL
  2. Click on one non 0.00 entry
  3. In the regex field, add: (\d+)
This will only show the value for decimals+ (no cents) but that is enough for our use-case. Once that is done, tell BPA to treat the
value as a metric. For this, open the "Advanced Settings" tab at the bottom of the tile and change it accordingly.

Recurrent Transactions discovery settings

Next, we configure the discovery settings (top right of the page)
and finally, apply all settings so these get pushed out to the BT Listener.
 
Wait 5 minutes, and check the metric path on the DxC. For this go to:
  1. Triage
  2. Metrics/Traces by Agent
  3. Experience Collector Host
  4. Business Segment
and open the entry starting with: [bpa-demo-docker]IP/PORT - the IP is the internal IP of your docker instance running the BPA.
 
If you want to see a real value show up and not wait for the traffic generator to produce one, go to your bpa-demo application, buy some
goods, check out and have a look at the metric tree. It will show your value that has been detected.

App eXperience Analytics (AXA) tuning step by step

The App Experience Analytics system is running as is out of the box once activated. We will however active 2 more things, notably enable the cookie capture (helps searching our sessions), and the funnel activity (identify how the user goes through the application).

Activate Cookies collection

On your DX O2 tenant, go to the settings => "Manage Mobile/Browser Web Monitoring", select the application "BPA Demo AXA docker", select the "Web App" tab and open the "+ Edit Profile"  tab on the lower left side.

Funnel activity, also known as Business Activity Configuration

Navigate to the top right of the "BPA Demo AXA docker" page and find the Business Activity Configuration link and select it.
We will be configuring 2 funnels:
  1. Login to checkout - add 10 steps
  2. Landing page to checkout - add 20 steds.

The aim of this configuration is to find out the "spots" the users leave the web-shop.

First one is to be configured as shown. Don't forget to save it (Create button).

The second one is to be configured as shown below. Note that the landing page / or index.php is automatically redirected to the /shop URL Path.
Make sure to save it (Create button).
This will enable us to see which path the users goes through the Web-page.

Conclusion

With the setup complete, our demo system is ready for action!


In our next post, we’ll take you on a guided tour of your collected metrics—showing you how to visualize the data and turn it into actionable insights. We'll also walk through practical, step-by-step use cases, demonstrating how to navigate everything from initial alarm triggers to root-cause troubleshooting. Stay tuned!

0 comments
4 views

Permalink