지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight for Microsoft DOT NET 5.9.13 - Installation and Configuration Guide

Installing and Configuring Foglight for Microsoft .NET Managing .NET Agent Configurations

Creating .NET Agent instances

Foglight for Microsoft .NET uses the .NET agent to collect information from monitored hosts. Creating a .NET agent instance creates the agent process (either locally, or on the monitored host).

Use the Application Servers Administration dashboard to create .NET agent instances.

 
* 
NOTE: This dashboard is common to Foglight for Microsoft .NET and Foglight for Java EE Technologies, versions 5.9.1 and later.
To create a .NET agent:
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
The Application Server Administration dashboard opens in the display area.
 
* 
IMPORTANT: The options available on this dashboard depend on the application server monitoring capabilities that you have installed (for example, Java Administration is only available if you have installed Foglight for Java EE Technologies).
2
In the Monitoring Agents section, click Setup agents...
3
In the list that opens, click .NET. The .NET Setup wizard opens.
4
On the Setup Options page, select the type of .NET agent to create, depending on whether you want to monitor Transactions and performance counters or Performance counters only.
Transaction monitoring - Install the agent on the monitored host. This means that you must have an Agent Manager deployed to the monitored host. For more information, see Creating a .NET transaction and performance counters monitoring agent.
Performance-counter-only monitoring - Install the agent either on the monitored host or on a remote host. For remote hosts, review the topic Configuring a remote host for .NET performance counters monitoring before continuing with Creating a .NET performance-counters-only monitoring agent .

Creating a .NET transaction and performance counters monitoring agent

Before you begin

Ensure that you have installed and activated a compatible version of the Foglight Agent Manager on the monitored host. If you are not familiar with this process, see the Foglight Agent Manager Guide.

 
* 
NOTE: You cannot create a transaction and performance counters monitoring agent on a host that already has an existing .NET performance counters monitoring agent installed locally.

This procedure continues from the end of the procedure To create a .NET agent: .

To create a Transaction and Performance Counters Monitoring Agent:
1
On the Setup Options page, select Transactions and performance counters and click Next.
2
On the Monitored Hosts page, select one or more hosts for the .NET agent.
 
* 
IMPORTANT: By default, only eligible hosts (hosts that have an active, compatible Agent Manager and that are not being monitored by a performance counters agent) are shown. To view all hosts, click Show eligible hosts only. The Monitored Hosts page refreshes and all hosts are shown.
Select hosts from the list and click Next.
3
On the Integration Configuration page, select whether you want to create a configuration or reuse an existing one. This configuration controls whether the IIS is integrated, and specifies which Windows® Services and standalone applications are integrated.
To learn about reusing an existing configuration, see Reusing .NET transactions and performance counters integration .
For this example, select Create new configuration, and click Next.
4
On the New Integration Configuration page, specify integration targets for the agent. These targets can include IIS, Windows Services, and standalone applications.
•
Integrate with IIS is enabled by default. If you do not want to integrate with IIS, clear this check box.
•
To integrate with a Windows Service, click Add Windows Service.
A row appears in the list, with the Process Type specified as Windows Service.
Click the Name box, and type the name of the Windows Service. This must be the service name, not the display name.
•
To integrate with a standalone application, click Add standalone application.
A row appears in the list, with the Process Type specified as Standalone Application.
Click the Name box, and type the full path to the executable.
After you have specified all the targets for integration, click Next.
5
On the Transaction Agent — Nexus Connection page, select or create the connection that the agent should use to connect to the Nexus.
 
* 
TIP: For more information about the Nexus, see Understanding the Nexus and agent-Nexus connections for .NET agents .
If you are using the default Nexus on the embedded Agent Manager, or if you have created a single remote Nexus, a default Nexus Connection is created and pre-selected for you. Otherwise, select or define at least one Nexus connection.
To define a Nexus connection:
a
Click New Nexus connection. The New Nexus Connection dialog box opens.
b
Click Add Nexus location and select a Nexus from the list.
or
Click Add Nexus location and then click Add custom to define a new Nexus location by specifying the listen address and port. The default listen port is 41705. For example: hostname.company.com:41705.
c
Optional — To add another Nexus location, click Add Nexus location again.
 
* 
IMPORTANT: If you add more than one Nexus, the agent attempts to connect to a Nexus in the order specified on this screen until it succeeds.
d
Type a unique name for the Nexus connection in the Save as box.
e
Optional — Click the Advanced tab to review and edit the connection settings. Click the icon to view a detailed description of the setting and its effects.
f
Click Save.
g
Click Next.
6
On the Transactions Agent — Configuration page, select the configuration that defines the instrumentation settings for the agent.
The .NET Default configuration is selected automatically if no other configurations exist.
 
* 
TIP: You can modify configurations, or assign new configurations to an existing agent, at any time after the agent has been created. For more information, see Managing .NET Agent Configurations .
Click Next.
7
On the Domain Assignment page, leave the Assign servers the following domain box blank to automatically assign monitored hosts to their Windows domain or workgroups.
To select a different domain:
•
Click the down arrow in the Assign servers the following domain box to open a list of known domains.
•
Type a domain in the Assign servers the following domain box.
Click Next.
8
On the Installation Directory page, define the location for the directory that contains all installation components. To accept the default directory, leave the Directory name box blank.
 
* 
IMPORTANT: If you have previously configured the host for a .NET agent installation, the existing installation directory is used.
To specify a custom directory, type a path in the Directory name box.
Click Next.
9
On the Review page, verify the configuration for the agents.
a
Type a name for the integration configuration in the Name box. Use a specific, unique name so that you can identify this integration for reuse.
b
By default, the Activate agents* check box is selected. It is recommended that you leave this option enabled. If you disable it, you must manually activate the agents and start data collection from the Application Servers Administration dashboard.
 
* 
NOTE: Restart the target IIS servers, Windows Services, or standalone applications to complete the integration process.
c
If the information is correct, click Finish.
The Monitoring Task History section of the dashboard updates. For more information, see Viewing .NET agent task history.

The agent connects and begins collecting data. To view the data, open the Application Servers Monitor dashboard (Dashboards > Application Servers > Monitor). For more information about this dashboard, see the Foglight for Application Servers User Guide.

Configuring a remote host for .NET performance counters monitoring

The .NET performance counters monitoring agent can be installed locally (that is, on the same host that it is monitoring) or remotely. There are several configuration steps that may be required to ensure that a remote agent can connect and monitor a host.

Keep the following general comments in mind:

•
Any access-denied errors are related to permissions and DCOM errors rather than WMI.
•
RPC errors are related to firewall rules, rather than DCOM or WMI.
•
Provider errors are related to WMI and could be caused by permissions on objects or namespaces.
To ensure successful remote monitoring of performance counters:
1
Start the remote registry service.
2
Configure the Windows® firewall in one of the following two ways:
•
Disable the firewall.
or
•
Enable traffic through Windows Management Instrumentation (WMI) and allow a remote administration exception.
For more information about WMI, see:
http://msdn.microsoft.com/en-ca/library/windows/desktop/aa822854%28v=vs.85%29.aspx
For more information about allowing remote admin exceptions, see:
http://msdn.microsoft.com/en-us/library/aa389286.aspx
3
Review the information about Handling Remote Connections Under UAC:
http://msdn.microsoft.com/en-ca/library/windows/desktop/aa826699%28v=vs.85%29.aspx
Follow the recommendations for providing:
a
Remote launch and activate rights to access DCOM.
b
Rights to access the WMI namespace remotely (Remote Enable).
4
For a host in a workgroup, disabling Remote UAC by changing the registry entry that controls Remote UAC may be required. The registry entry is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system\LocalAccountTokenFilterPolicy
Set the value of this entry to 1 to disable Remote UAC.

Creating a .NET performance-counters-only monitoring agent

If you are creating a performance counters monitoring agent, and you want to be able to add transaction monitoring on the same host in future, ensure that you create the agent remotely. That way, you can create a transaction and performance counters monitoring agent locally at a later time.

Before you begin

Make sure that you have reviewed the information in Configuring a remote host for .NET performance counters monitoring and that the necessary configuration is complete.

This procedure continues from the end of the procedure To create a .NET agent: .

To create a Performance Counters Monitoring Agent:
1
Select Performance counters only and click Next.
2
On the Monitored Hosts page, select the hosts that you want to monitor in one of the following ways:
•
Click Select hosts from a list to open a list of hosts that are known to Foglight.
In the Select Known Hosts dialog box, select one or more hosts from the list, or use the search box to locate a host. Click OK to close the box and save your entries.
•
Click Enter host names to type the host names in a list.
In the box that opens, type one or more host names separated by either commas or new lines. Click OK to close the box and save your entries.
 
* 
IMPORTANT: In order for a .NET agent to connect to and monitor a Windows host, it must have access to an account with Windows® Administrator privileges. Ensure that a credential exists and has been released to the Agent Manager. For information about creating and managing credentials, see the topic Controlling System Access with Credentials in the Foglight Administration and Configuration Help.
Click Next.
3
On the Agent Host page, select the Agent Manager that you want to use to manage the .NET agent you are creating.
Click Next.
4
On the Agent Names page, accept the default naming scheme, or customize the name on a per-agent basis.
To change the agent naming scheme, click Edit in the Agent Name column of the monitored host’s row.
Click Next.
5
On the Integration Configuration page, select whether you want to create a configuration or reuse an existing one. This configuration controls whether the IIS is integrated, and specifies which Windows Services or standalone applications are integrated.
To learn about reusing an existing configuration, see Reusing a .NET performance-counters-only integration configuration .
For this example, select Create new configuration, and click Next.
6
On the New Integration Configuration page, specify integration targets for the agent. These targets can include IIS, Windows® Services, and standalone applications.
•
Integrate with IIS is enabled by default. If you do not want to integrate with IIS, clear this check box.
•
To integrate with a Windows Service, click Add Windows Service.
A row appears in the list, with the Process Type specified as Windows Service.
Click the Name box, and type the name of the Windows Service. This must be the service name, not the display name.
•
To integrate with a standalone application, click Add standalone application.
A row appears in the list, with the Process Type specified as Standalone Application.
Click the Name box, and type the full path to the executable.
After you have specified all the targets for integration, click Next.
7
On the Domain Assignment page, leave the Assign servers the following domain box blank to automatically assign monitored hosts to their Windows domain or workgroups.
To select a different domain:
•
Click the down arrow in the Assign servers the following domain box to open a list of known domains.
•
Type a name in the Assign servers the following domain box.
Click Next.
8
On the Installation Directory page, accept the default directory for installed components and log files, or specify a custom directory.
 
* 
IMPORTANT: Only one installation directory is allowed per host. If an installation exists, a message appears to indicate this.
To specify a custom directory, type the path in the Directory name box.
Click Next.
9
On the Review page, verify the configuration for the agents.
a
Type a name for the integration configuration in the Name box. Use a specific, unique name so that you can identify this integration for reuse.
b
By default, the Activate agents and start data collection* check box is selected. It is recommended that you leave this option enabled. If you disable it, manually activate the agents and start data collection from the Application Servers Administration dashboard.
c
If the information is correct, click Finish.
The Monitoring Task History section of the dashboard updates. For more information, see Viewing .NET agent task history.

The agent connects and begins collecting data. To view the data, open the Application Servers Monitor dashboard (Dashboards > Application Servers > Monitor). For more information about this dashboard, see the Foglight for Application Servers User Guide.

Related topics
•
Reusing .NET agent integration configurations
•
Editing .NET thread metrics integration configurations
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택