Overview of End User Monitoring

Note: Custom metrics for EUM Analytics are not supported in on-premises environments.

Splunk AppDynamics End User Monitoring (EUM) gives you visibility on the performance of your application from the viewpoint of the end user.

While Application Performance Monitoring (APM) measures user interaction starting at the web server or application server entry point, EUM extends that visibility all the way to the web browser, mobile, or IoT application. As a result, EUM reveals the impact the network and browser rendering time have on the user experience of your application.

The diagram below provides an overview of the different components, deployment models (SaaS/on-premise), and the Controller UI as seen by Splunk AppDynamics end users. The SaaS deployment employs services (Controller Service, Events Service, EUM Service, EUM Synthetic Monitoring Service) to collect, store, and process data, whereas, the on-premise deployment requires customers to install discrete components such as the Controller and servers (Events Server, EUM Server) that run processes to collect, store, and process data.

Annotations are provided for each label below the diagram.

End User Monitoring Diagram

StepDescriptionComponent(s)

The Browser, Mobile, and IoT Agents run in web/mobile/IoT applications, collect metrics, and then transmit that data to either a SaaS or an on-premise deployment of Splunk AppDynamics.
  • Browser/Mobile/IoT Apps
  • EUM Agents

The consisting of the components listed to the right, stores, processes, and analyzes data, and then delivers RUM metrics to the Controller UI.
(A)Controller Service - stores data and metadata, makes calls to the EUM Server for raw data and the Events Service for analytic data.
(B)Events Service - stores short-term RUM data (such as sessions, network requests, snapshots) for heavier analysis.
(C)EUM Service - verifies, aggregates, and packages raw browser/mobile app metrics.
(D)EUM Synthetic Monitoring Service - schedules and executes Browser Synthetic jobs and returns session data to the Controller.

The Splunk AppDynamics On-Premises has most of the same components and data as the . In this model, DevOps install and administer their own Controller, Events Service, and EUM Server.
  • Controller
  • Events Server
  • EUM Server
Note: See the descriptions for each component above in step 2. The EUM Server performs the same functions as the EUM Service.

Splunk AppDynamics users can go to the Splunk AppDynamics Controller UI to view and analyze RUM metrics as snapshots, pages, Ajax requests, sessions, network requests, or in the form of charts and graphs.

Controller UI

Note: See the description for the Controller UI in step 2.

Understand End User Activity

Using EUM, you can determine:

  • Where geographically your heaviest application load is originated.
  • Where geographically your slowest End User response times occur.
  • How performance varies by
    • location.
    • client type, device, browser and browser version, and network connection for web requests.
    • application and application version, operating system version, device, and carrier for mobile requests.
  • What your slowest web/Ajax requests are, and where the problem may lie.
  • What your slowest mobile and IoT network requests are, and where the problem may lie.
  • How application server performance impacts the performance of your web and mobile traffic.
  • Whether your mobile or IoT applications are experiencing errors or crashes and the root cause of the issues. For example, for mobile applications, EUM provides stack traces and event trails for the crash or error, helping you troubleshoot and optimize mobile applications.

View EUM Data

The performance information generated by EUM is distinct from the application monitoring data generated by app server agents.

EUM data appears in various locations in the Controller UI, including in the User Experience dashboard, Metric Browser, and Splunk AppDynamics Analytics pages.

When linked to application business transactions, EUM data gives you a complete view of your end users' experience from the client request, through the application environment, and back to the client as the user response.

You can view EUM performance data in the Controller UI in the User Experience tab. From there, you can access information specific to browser applications, mobile applications, or connected devices (IoT applications).

オンプレミスの EUM 展開

デフォルトでは、EUM は EUM クラウドと呼ばれる Splunk AppDynamics ホステッドコンポーネントを使用するように構成されています。完全にオンプレミスのインストールでは、EUM サーバーが EUM クラウドの機能を提供します。詳細については、「EUM サーバーのデプロイ」を参照してください。

EUM の一部の機能は、Splunk AppDynamics プラットフォーム イベント サービスに依存します。SaaS 環境では、これは Splunk AppDynamics によって管理されますが、オンプレミスの形でこの機能を使用することもできます。

イベントサービスをオンプレミスでホストするには、次を参照してください。

既存のオンプレミスのコントローラインストールに EUM を追加する場合は、現在の構成で EUM による追加の負荷を処理できるかを評価する必要があります。詳細については、「コントローラのサイズ指定」を参照してください。

access-eum-cloudSaaS EUM サーバへのアクセス

 SaaS EUM サーバは、以下に示すコンポーネントで構成されています。各コンポーネントには、コントローラの地域に応じて異なるエンドポイントが存在する場合があります。

  • EUM サービス：モバイルエージェント、JavaScript エージェント、および IoT SDK は、EUM サービスにデータを送信します。コントローラは、EUM サーバからデータを取得します。
  • イベントサービス：EUM サーバは、イベントサービスに分析データを送信します。コントローラもまた、イベントサービスに対してクエリを実行します。
  • 合成サービス：合成プライベートエージェントと合成ホステッドエージェントは、合成サービスにデータを送信します。

SaaS またはオンプレミス展開でインターネット上のこれらのコンポーネントのいずれかにアクセスする必要がある場合は、SaaS ドメインと IP 範囲で指定された URL がネットワークからアクセス可能であることを確認してください。

注: ただし、オンプレミス展開では、EUM サーバーはインターネット上に配置することも、独自のデータセンター/ネットワーク内でホストすることもできます。オンプレミス アクセス ポイントは、インストール時に構成するか、または UI を使用して構成します。サポートされている SFP および SFP+ モジュールのリストについては、

EUM サーバーのデプロイ

」を参照してください。

How EUM Works with other Splunk AppDynamics Products

This section describes how other App iQ Platform products work with EUM to provide complete, full visibility on application health and user experience.

EUM and Application Performance Monitoring

Using APM with EUM provides you with greater insight into how the performance of your business application affects the end-user experience. To integrate APM with EUM, you correlate business transactions with browser snapshots. This enables you to trace bad user experiences to issues with your backends such as an unresponsive web service, bad database query or slow server response. To learn how to integrate APM with EUM, see Correlate Business Transactions for Browser RUM.

You can also use the app server agents running on business applications that serve your browser applications to inject JavaScript agent into the code that runs on the browser. This obviates the need to manually inject the JavaScript agent. For more information, see Automatic Injection and Assisted Injection.

Note: You must assign unique names to EUM applications and business applications. For example, if you created the business application "E-Commerce", you cannot create a browser, mobile, or IoT application with that same name or vice versa.

EUM and Application Analytics

Application Analytics enables you to use the powerful Query Language to analyze different types of EUM data through complex queries. The Analytics components are based on the Events Service, which is also the source of data for Browser Analyze, Crash Analyze, Network Requests Analyze, and all IoT data. Analytics requires a license separate from the EUM licenses except for IoT Monitoring.