.NETティアの命名
Splunk AppDynamics におけるティアとは、ASP.NET フロントエンド、WCF サービス、.NET ウェブサービス、またはスタンドアロン アプリケーションといった、アプリケーション環境内のサービスを表します。ティアはフローマップに表示されるため、ユーザーにとって論理的でわかりやすい名前を付ける必要があります。
IIS サイトをティアにマッピングするには、「.NETエージェントの構成」で説明しているように、Splunk AppDynamics .NET エージェント構成ユーティリティを使用します。一部の手動設定オプションでは、 .NETエージェントの管理 ファイルを編集する必要があります(「」を参照)。
Name IIS Tiers Automatically
Name IIS tiers automatically using the configuration utility. Select Automatic on the Assign IIS applications to the tiers pane.The .NET Agent instruments all IIS sites except the Default Web Site and names the tiers using this scheme:
IIS site/appThe agent omits app when the application is the root application for the IIS site.
Use this option when:
- You are new to Splunk AppDynamics and the .NET Agent.
- You want to instrument all IIS applications, and your team understands the form of IIS application names.
Name Azure Tiers Automatically
The .NET Agent automatically names Azure tiers using these schemes:
- Cloud Services:
Azure role name - App Services:
Azure site name
To customize tier naming for Azure, see Name IIS Tiers Manually.
Name IIS Tiers Manually
The .NET Agent provides two options to name IIS tiers manually, using the configuration utility, or editing the config.xml file directly.
Use the Configuration Utility
On the Assign IIS applications to tiers pane, select Manual. The configuration utility enables you to create new tiers and assign IIS applications to tiers.
Use this option when:
- You do not want to instrument all IIS applications on the server
- You want custom tier names
- You want to assign multiple applications to a single tier
Edit the config.xml Directly
Use this option to customize Azure tier names, or when it is not possible to use the configuration utility.
For each IIS tier to instrument, add an application element as a child element of the IIS applications element in the config.xml file. You can specify a static IIS tier name ,or a regular expression (which is helpful for variable Azure site names). For the full syntax and an example, see .NET Agent Configuration Properties.
For example, to add all Azure sites that begin with MvcWebRole to a tier named My Azure Tier using a regular expression:
<?xml version="1.0" encoding="utf-8"?>
<appdynamics-agent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<controller host="nativedemocon1.cloudapp.net" port="8090" ssl="false">
<application name="AzureEmailService" />
<account name="customer1" password="APJC234bcd$123" />
</controller>
<machine-agent />
<app-agents azure="true" azure-role-name="" azure-role-instance-id="">
<IIS>
<applications>
<!-- Configure IIS tier names with a regular expression. -->
<application path="/" site="MvcWebRole.*" site-regex="true">
<tier name="My Azure Tier"/>
</application>
</applications>
</IIS>
<standalone-applications>
<standalone-application executable="WaWorkerHost.exe">
<tier name="" />
</standalone-application>
</standalone-applications>
</app-agents>
</appdynamics-agent>
Name Windows Service or Standalone Application Tiers
See Configure the .NET Agent for Windows Services and Standalone Applications on how to name tiers for each instrumented Windows service or standalone application manually in the config.xml.