Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight for Microsoft DOT NET 5.9.12 - Installation and Configuration Guide

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

Reusing .NET agent integration configurations

After you have created your first .NET agent, you can reuse the integration configuration to create additional agents that use the same integration targets and settings.

Related topics
•
Reusing .NET transactions and performance counters integration
•
Reusing a .NET performance-counters-only integration configuration .

Reusing .NET transactions and performance counters integration

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

To reuse an existing integration configuration:
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.
 
* 
TIP: To learn about creating a configuration, see Creating a .NET transaction and performance counters monitoring agent or Creating a .NET performance-counters-only monitoring agent .
For this example, select Reuse existing configuration, and click Next.
4
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 .
Select or define at least one Nexus connection for the agent you are creating.
Click Next.
5
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.
6
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.
or
•
Type a domain in the Assign servers the following domain box.
Click Next.
7
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.
8
On the Review page, verify the configuration for the agents.
d
By default, the Activate agents* 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.
 
* 
NOTE: Restart the target IIS servers, Windows Services, or standalone applications to complete the integration process
e
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.

Reusing a .NET performance-counters-only integration configuration

Prerequisite:
•
Review the information in Configuring a remote host for .NET performance counters monitoring , and complete the necessary configuration.

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

To reuse an existing Performance Counters Monitoring Agent integration configuration:
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.
or
•
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 and standalone applications are integrated.
a
Select Reuse configuration.
b
Select an existing configuration from the list.
c
Click Next.
6
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.
or
•
Type a name in the Assign servers the following domain box.
Click Next.
7
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.
8
On the Review page, verify the configuration for the agents.
d
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, you must manually activate the agents and start data collection from the Application Servers Administration dashboard.
e
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.

Viewing .NET agent task history

The Task History section of the Application Servers Administration dashboard displays a list of agent-related tasks, such as Setup .NET Performance Counter Monitoring (1 agent).

The results of the task appear in the Results column.

To view detailed task information:
•
Click the Result text (for example, Success, or Timeout) to open the Task Result log.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation