Chatee ahora con Soporte
Chat con el soporte

Foglight for Microsoft DOT NET 5.9.13 - Application Servers Administration and Configuration Guide

Managing advanced configuration settings for all Nexuses

All Nexuses use the advanced configuration settings available from the Nexus Administration page .

 
* 
CAUTION: Do not change these settings unless instructed to do so by Quest Support.
To access the advanced settings:
1
On the navigation panel, under Dashboards, click Application Servers > Administration.
2
On the Application Servers Administration dashboard, click the Nexuses tab.
3
On the Nexuses view, click the Recording Settings tab and click Advanced configuration.
The Nexus Advanced Configuration page opens.
4
Click Show fully qualified names to show the full path to the file, relative to the Nexus installation folder.
5
Click the name of a file to open a Configuration Category Editor for that file.
 
* 
TIP: You can reset these settings to the original defaults by selecting the files you want to revert and clicking Reset to factory defaults. Any changes you have made are discarded.

 

Managing Actions

The Application Servers > Manage Actions dashboard allows you to use actions to gather additional information from your monitored environment.

To access the Manage Actions dashboard:
•
On the navigation panel, under Dashboards, click Application Servers > Nexus > Administration > Manage Actions.
Application server actions

Use the Manage Actions dashboard to create actions to integrate with other Foglight cartridges or systems. The following default actions are available:

 
Table 4. Default actions for integrating with other Foglight systems.
Action
Description

FxV: Search Hits (request UUID)

Search hits in FxV using the request UUID.

FxV: Search Hits
(request type, JESSIONID)

Search hits in FxV using request type and JESSIONID around the time the trace occurred1.

FxV: Search Hits
(request type)

Search hits in FxV using request type around the time the trace occurred1.

FxV: Explore Session (JSESSONID)

Explore session in FxV using JESSIONID around the time the trace occurred.

FxV: Search Hits
(request type, parameter)

Search FxV using request type, parameter name and value around the time the trace occurred1.

 
* 
IMPORTANT: Do not edit any of these default actions.

These default actions are specific to Foglight Experience Viewer (FxV) integration. For more information about integrating with FxV, see Managing Request Integration with Foglight Experience Viewer .

You can create your own actions using a Groovy Script, as described in Creating actions.

Creating actions

You can use actions to collect additional information about your monitored environment. Actions are defined using Groovy scripts, and can apply to specific contexts, such as trace parameters, requests, or traces.

To create an action:
1
On the navigation panel, under Dashboards, click Application Servers > Nexus > Administration > Manage Actions.
2
Click Add.
3
In the Menu Item Text box, type the name you want to display in the action menu.
4
Optional — in the Description box, type a brief description for this action.
5
Select the Open in new window check box if you want the action to open in a new browser window.
 
* 
NOTE: This action varies depending on the web browser options you have set. You can have your options set to open a new window or a new tab in the current session.
6
In the Action Groovy Script box, type the Groovy script you want to apply.
This Groovy script is used to return an HTTP URL string that opens either a new web browser window or a Foglight for Application Servers WCF Iframe view.
For example, to open our company web page, type:
return "http://www.quest.com/";
7
In the Apply To selection, select one or more of the following contexts:
•
Request — Adds an action to the Request tab Action
•
Trace Parameter — Adds an action to the Single Trace HTTP Parameters table
•
Trace — Adds an action to the single trace Action column menu
8
Optional — in the Menu Item Display Groovy Script field, enter a Groovy script that evaluates to a boolean value. Users can use this to add extra logic to determine if an action should be displayed or not (for example, checking if FxV Integration is configured). If you leave this box blank, the menu item is always displayed.
The following example shows the action only if the request is not an HTTP request:
return !appserverAction_isHTTPRequest(@requestName);
9
Click OK. The dialog box closes and the Manage Actions dashboard refreshes.

Using variables in action Groovy scripts

The following table outlines some of the available action variables you can use when writing your custom Groovy scripts, and to which action menus the variables are applicable.

 
Table 5. Variables available for use in custom Groovy scripts.
Variable
Description
Single Trace
Request
Single Trace Parameter

@requestType

Request Type.

Y

Y

Y

@trace

Request Trace value.

Y

N

Y

@requestName

The name of the request.

Y

Y

Y

@specificTimeRange

A specific time range (the time range of the view).

Y

Y

Y

@traceParameters

The name-value pair of the parameters of the single trace.

Y

N

Y

@traceStartTime

The time when the trace started.

Y

N

Y

@parameterType

The type of parameter of a single trace. For example type a string for a field, cookie, or header.

N

N

Y

@parameterName

The name of the selected parameter.

N

N

Y

@parameterValue

The value of the parameter.

N

N

Y

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación