Chat now with support
Chat with Support

Foglight for Microsoft DOT NET 5.9.7.5 - Installation and Configuration Guide

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

Creating Collection Schedules

You can create a custom collection schedule to control the collection types and intervals for particular agents.
To create a custom schedule:
1
On the navigation panel, under Dashboards, click Application Servers > Administration > Application Servers Administration.
2
On the Application Servers Administration dashboard, click .NET Administration.
3
On the .NET Administration dashboard, click the Collection Schedules tab.
4
On the Collection Schedules view, click New collection schedule.
The New Collection Schedule dialog box opens.
5
For each collection type, select a collection interval. Click the interval value (for example, 24 hours) to open a list of values.
If you need more information about a particular collection type, or if you want to double-check the default recommended value, click the icon for that type.
6
Type a name for the new custom schedule in the Schedule name box.
7
Click Save.
The dialog box closes, and the Collection Schedules view refreshes. You can now assign the custom schedule to one or more agents. For more information, see Assigning Custom Collection Schedules to an Agent.

Assigning Custom Collection Schedules to an Agent

After Creating Collection Schedules, you can assign the newly created schedules to .NET agents.
To assign a custom schedule to an agent:
1
On the navigation panel, under Dashboards, click Application Servers > Administration > Application Servers Administration.
2
On the Application Servers Administration dashboard, click .NET Administration.
3
On the .NET Administration dashboard, click the Collection Schedules tab.
4
On the Collection Schedules view, click the name of the schedule that you want to assign to one or more agents.
5
In the list that opens, click Assign to agents.
The Assign Collection Schedule - <schedulename> dialog box opens.
6
Select one or more agents from the list.
7
Click Assign.
The dialog box closes and a message box opens, verifying that the schedule was assigned to the selected agents.
8
Click OK to close the message box.

Increasing WMI Polling Memory Values

DN-834 DN-1051 By default, the .NET agent can monitor up to 250 total objects when the default values for Polling WMI Memory Per User and WMI Polling Memory Total are used. This total object count includes the number of web sites, the number of web applications, and the number of application pools.
For environments with higher object counts, you may need to increase both of the Polling Memory values to ensure that a quota violation error is not triggered.
 
* 
NOTE: These changes apply only to local agents. They have no effect on remotely hosted counter agents.
To increase the polling memory values:
1
On the Application Servers Administration dashboard, click the name of the monitoring agent for which you want to adjust the memory values.
2
In the menu that opens, click Properties.
3
At the bottom of the Agent Properties dialog box, click the down arrow beside Advanced Settings.
4
Adjust the values for either the Total or the Per User polling memory as necessary.
WMI Polling Memory Per User is the maximum amount of memory that can be consumed when polling event queries issued by a particular user. Default value is 25 MB.
WMI Polling Memory Total is the total amount of memory that can be consumed when polling event queries issued by all users. Default value is 50 MB.
5
Click OK.
6
Stop and restart the data collection.

Preventing WMI Quota Violations

In some cases, due to the limitations on the length of query strings for web applications, application pools, and sites, a WMI Quota Violation may be encountered.
When this issue occurs, the following error message appears in the agent log:
The agent can only monitor a subset of all specified IIS configuration objects due to WMI query string limit. Consider adjusting the Included/Excluded settings for Web Applications, Application Pools, and Sites.
If you see this message, refer to the following section for information about adjusting the included/excluded settings: Editing IIS .NET Integration Configurations .
 
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating