EUM アカウント、ライセンス、およびアプリケーションキー

このページでは、エンドユーザモニタリング（EUM）のアカウントおよびライセンス情報について説明します。

ライセンス使用状況の表示

EUM ライセンスの使用量をコントローラに表示するには、歯車アイコン > [License] の順に移動します。

超過料金

ライセンスが超過分を許可しない場合、Splunk AppDynamics はライセンス制限に達した後にメトリックの報告を停止します。ライセンスで超過が許可されていて使用量が制限を超えた場合、Splunk AppDynamics は EUM メトリックのレポートを継続し、ライセンス契約によって規定された単位レートで超過分を請求します。

ライセンスキー

EUM ライセンスタイプが少なくとも 1 つある場合は、EUM アカウントがあり、名前とライセンスキーが関連付けられています。これは、Splunk AppDynamics が EUM データをアカウントに関連付けるために使用する固有識別子です。この情報はトラブルシューティング目的でのみ知っておく必要があります。4 つの EUM サービスすべてに同じキーが適用されます。ただし、各製品には、許可される使用法に関する独自のタイプとメトリックがあります。

EUM アプリケーションキー

これは、Splunk AppDynamics がエンドユーザーデータを特定の EUM アプリケーションに関連付けるために使用する固有識別子です。各 EUM アプリケーションは、1 つの EUM アプリケーションキーに関連付けられます。モニター対象のアプリケーションについては、データのレポート時に EUM アプリケーションキーを含める必要があります。EUM アプリケーションキーは、EUM アカウント名とライセンスキーにも関連付けられます。

注: ライセンスキーを変更しても、既存の EUM アプリケーションキーには影響しません。

License Optimization and Usage Periods

For EUM license metric definitions and data retention, see License Entitlements and Restrictions.

EUM LicenseLicense OptimizationUsage Period
Real User MonitoringSee Browser and Mobile RUM rows below.See the Browser and Mobile RUM rows below.
Browser RUMIf the value of Pageviews is greater than Pageviews Allocated and your license allows overages, you are incurring overage charges. If you need to stop incurring overage charges, you can disable Browser RUM to stop end user monitoring and stop Pageviews from being charged (once disabled, expect a delay of approximately one minute).The Browser RUM usage period is per year, even if you have a multi-year license. The meter resets every year based on the expiration of your license agreement. For example, if your license expires at 12:00pm PST on May 1, 2020, your usage period resets every year starting 12:00pm PST on May 1, 2021.
Mobile RUM

License consumption is affected when you have one instrumented application installed on multiple devices, multiple applications on the same device, or uninstalls followed by reinstalls:

  • If you install one instrumented application on two devices within a month, each device uses one Monthly Active Agent.

  • If you uninstall and then reinstall an instrumented application multiple times within a month, each reinstall uses one Monthly Active Agent.

  • If you install two different instrumented applications on the same device within a month, each instrumented application consumes one Monthly Active Agents, so.

Through SDKs, you can customize application instrumentation to choose which agents send data. For further instructions, see the following:

The Mobile RUM usage period begins and the meter resets on the first day of each month at 12:00pm PST. When your license consumption reaches 90% of your Monthly Active Agent allocation, you will see a warning in the Mobile RUM dashboard.
Synthetic

To help you optimize the use of your Synthetic Agent license, keep the following in mind:

  • Synthetic jobs are measured in terms of the time it takes to actually run the test in Splunk AppDynamics systems. Because it is not possible to know in advance how long a given test may take, you can set a timeout value when you create the job. If the job times out, you receive partial results.

  • Once you have used up your monthly allotment, all synthetic jobs are paused until the following month.

  • If there is a problem accessing a site, such as receiving a 5xx error, the system automatically runs the job again. You are charged for these retests.

  • If you see a session with the status INTERNAL_ERROR, this means there is a problem with Splunk AppDynamics infrastructure, and you will not be charged, even if the session contains partial results.

  • Adjusting synthetic job configurations, such as the number of browser types, frequency, and duration, may have an impact on license consumption. To gauge estimated consumption in the Controller, create a new job and see the section Set a Timeout (step 6).

  • Locations are user-defined. You can add multiple servers (agents) to a location to increase capacity, and this does not impact your license.
The usage period begins and the meter resets on the first day of each month at 12:00pm PST.
IoT

License consumption is based on Application Instances. We recommend that you register each Application Instance and each device so that you can correlate data with each data source. To reduce license consumption, you can register just one device with multiple Application Instances, or one Application Instance on multiple devices. However, in doing so, Splunk AppDynamics cannot differentiate data, such as errors, for each application instance or device unless each one is registered.

The usage period begins and the meter resets on the first day of each month at 12:00pm PST. The usage period for IoT is always the current month, even if you have a multi-year license.