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

Foglight for Databases 6.1.0 - User Guide

Getting Started Viewing, Acknowledging, and Clearing Alarms Viewing, Creating, and Managing Alarm Templates Monitoring Your Domains Monitoring Your Services Monitoring Your Hosts Reporting on Your Enterprise

Online-Only Topics

Building a service

A service is a grouping of one or more components that interest you. Use the Service Builder dashboard to group monitored resources into services.

If you have the Advanced Operator role, you can use this dashboard to create a new service and edit existing services. When you create a service, a corresponding service level is automatically created.

In addition to the My Services dashboard, services appear in other dashboards (such as Hosts and Agents), as well as in reports. Defining a good set of services makes other dashboards more useful and easier to understand.

For more information, see the following topics:

•
Creating a service
•
Structuring a service
•
Classifying services
•
Adding a new category
•
Adding Service Components
•
Creating Custom Object Groups
•
Creating a Service Contained by Another Service
•
Adding a Rule-based Group of Components
•
Editing a Service
•
Removing a Service, Category, or Monitored Component
•
Associating Email Addresses with a Service
•
Filtering Alarms
Creating a service
To create a service:
1
On the navigation panel, under Dashboards, click Services > Service Builder.
2
Add different elements to your service. See Structuring a service.
Structuring a service

When you create a service, you add different elements that compose its structure:

•
A category, which is a top-level service. For example, a department or application set. See Adding a new category for instructions on how to add a category.
•
Other services contained within the category. For example, a team within the department or one application in the set. See Creating a Service Contained by Another Service for instructions on how to create a service.
•
Components, which can be added directly to the category or to the services it contains. For example, a specific host or a rule-based set of components. See Adding Service Components for instructions on how to add components.

For example, you want to create a top-level service called Applications that contains your Banking Application and Customer Survey Application. First, you need to create a category, then add the services and components you want it to contain.

Classifying services

You classify the services you create as a global (common) service or a local (custom) service.

Use a global service if you want to define a single service and use it in multiple services. Since a global service is a common service, it must have a unique name in Quest Foglight. For example, if you have a service that monitors legacy systems that are used in many places, you can define a single global service called Legacy Service, then re-use it wherever you need it.

A local service is local to the parent service. It is also known as a custom service. Use a local service if that service is unique to the parent service. When a service is local to its parent, its name must be unique under its parent, but you can use the same name to create other local services in other parents. For example, you might create a local service called Database in several parent services.

Adding a new category

A category is a top-level service. Create a new category to contain a hierarchy of related services if an appropriate category has not already been defined in your Foglight installation. You can create categories for a department, application set, business function, even a team or individual user.

For example, create a service called Accounting to monitor the performance of an accounting system. This accounting system has a web front-end for data entry and uses a Weblogic server and a SQL server in the back-end. The data collected on the end user response time, the Weblogic server, and the SQL server are added to this service as three separate components. By selecting Let Foglight Decide as the Tier, these components are assigned to their default tiers. Also, by setting Select components used to determine the availability of this service to Only components in selected tiers and selecting only the User tier, only the end user response time (for example, time spent posting transactions using the web interface) is used to determine the availability of this service. This is reflected in the Service Level Compliance column in the My Services dashboard.

To create a new category:
1
On the Service Builder dashboard, click Add A New Category.
Figure 78. The New Category Wizard opens.
2
Type a Name for the category.
 
* 
NOTE: You can change the name of a service at a later date, without losing all history for a service. See Editing a Service.
3
Optional — Enter text in the Short Description and Description fields. The text in the Description field appears in a dwell when you hover over a service.
4
Select a Tier. You can keep the default selection “Let Quest Foglight Decide” or optionally assign this service to a tier. Selecting a specific tier causes all objects in this service to be grouped under that tier.
5
From the Drilldown menu, you can specify a view to drill into from this service. Click Is not configured and select the view that Quest Foglight will use as the drilldown view from this service. If you have created a shared custom dashboard, this dashboard can be used as a drilldown view for this service. It also appears in the drilldown list under your user name and is available to other users with the same role permissions. In the example drilldown list below, the user test_user has the ability to set the custom dashboard called Test-dashboard as the drilldown view for this service.
Figure 79. Example of a drilldown list.
Once set, you can view this drilldown view from the My Services dashboard by clicking the icon.
Figure 80. Click the Explore icon.
6
Optional — From the Quest Foglight can automatically add hosts that support any object you add to your service option, you can disable this setting. By default it is enabled to dynamically add and maintain hosts in this service. Click No to disable this option.
7
Optional — Set the Objects used to determine the availability of this service option. These selected tiers will be used to evaluate the Service Level Agreement (SLA). Select one of the following options:
•
All components added to this service. This is the default option.
•
Only components in selected tiers. Select this option to specify the individual tiers that you want to include. Click the check box beside the tier name to include it.
By default, all objects contribute to the availability of a service. To customize the set of tiers from which components are added to this service, select the Only components in selected tiers check box and then select one or more tiers from this list.
 
* 
TIP: Tiers allow you to structure services in a way that best represents your monitored environment. By default, Foglight organizes data into a set of tiers, that includes User, Web, Application, and Database. You can create your own tiers. To learn more, see the “Associating Service Objects with Groups and Tiers” topic in the Administration and Configuration Guide.
8
Click Next.
9
Optional — Select the domains to associate with this service category.
By setting domains to associate with this new service, detailed service information can be reviewed in the Infrastructure dashboard for each set domain. To review these details, open the Infrastructure dashboard, select the service you just created, and click the Monitoring tab to view the domains assigned to this service.
 
* 
NOTE: Descriptions for the Domains are display if the Cartridge for Infrastructure is installed. Domains with no activity are not displayed in the Cartridge for Infrastructure until an activity is detected. For more information about the Infrastructure dashboard, see the Managing the Infrastructure Cartridge User and Reference Guide.
Figure 81. Assign domains.
10
Click Finish. The new top-level service is added to the Service Builder table.
Adding Service Components

You can specify the service components to monitor.

Figure 82. Add components to monitor.

To add components to a service:
1
Under the Actions column, click in the Add column for the service or category with which you want to work.
2
From the dialog box, click Add components to this service.
The Add components to this service dialog box appears. From here you can choose the components from a list of components, or you can create and add a rule-based group of components.
Figure 83. The Add components to this service dialog box.
3
Click Add specific component.
4
Find the type of component.
Figure 84. An example of the search features.
a
In the Name Containing field, type a search string.
b
Select a group using the From list, or by typing a keyword into the field, and then click Search.
You can use the Search and Advanced search features to find objects to add as components of a service.
The table and drop-down lists all instances from groups, such as:
•
Agents
•
All models
•
Hosts
•
Global Services provides a list of common services.
•
Hosts supporting objects added to this service. This option allows you to select some hosts and add them to the service, whereas the Yes/No field in the New and Edit Service dialog box is available for dynamic inclusion of all hosts. For more information, Adding a new category.
c
Optional — Create your own object group by clicking View Object Groups. See Creating Custom Object Groups.
d
In the Object(s) found table at the bottom of the dialog box, select the specific components you want to add to your Object group. Click Select All to quickly select components listed on the table. Click Unselect All to clear the selection. To locate a component by name and type, click Advanced. You can also use regular expressions.
5
Click Add Components.
The service components are added to the service that you chose in Step 1.
Creating Custom Object Groups

You can create your own object groups to collect instances for a specific object type. For example, you may be only interested in examining only CPU data for all instances in your environment.

To create an object group:
1
In the Add specific component dialog box, Step c, click View Object Groups.
2
In the Objects groups dialog box, click Add, and type a name and description for your custom Object Group.
3
Ensure the Is Disabled check box is cleared to enable the object group activation.
4
Click Create.
The subgroup table is displayed at the bottom of the dialog box.
5
Click Add to select the object groups from the table.
The Create Object SubGroup dialog box opens.
6
In the Name field, type a unique name for the subgroup. In this example, type Example.
7
Specify the Data Type, Query Conditions, and if it Is Disabled by default. Once done, click
8
Optional—click Test to review the results.
9
Click Create.
The custom object group is created and added to the Add specific components From menu.
Figure 85. The Add specific components menu.
Creating a Service Contained by Another Service

Add services to a category or nest services within other services to create a hierarchy that corresponds to your needs. For example, add a service called Production Servers to your category Server Room. You can then add services to Server Room that reflect the different server operating systems they run or the different applications they host.

To create a new service contained by a category or service:
1
In the Service Builder dashboard, expand the service hierarchy and click in the Add column.
2
In the dialog box, click Create a child service.
Figure 86. The Create a child service link.
3
Choose to create a Local or Global service.
•
New Local Service—creates a new local service and automatically attaches it to the selected service. As a local service, it is not listed in the Global Services and cannot be reused in different services.
 
* 
NOTE: If you are unsure of whether to create a Local or Global service, choose Local. Choosing Local avoids name clustering with other Global services. In most cases, new users should use Local service.
•
New Global Service—creates a new global service and automatically attaches the service to the selected service. A global service is designed to be reused in other services in the service model. Once added, it will be listed as one of the existing global services from which you can select.
 
* 
NOTE: A Global Services link is provided in the Actions panel of the Service Builder. This link takes you to the “Service Builder: Global Services” dashboard, which works the same way as the existing Service Builder. The only difference is that it is for adding, modifying, or deleting Global Services.
Depending on whether you selected a new local or global service, a new service dialog box appears.
Figure 87. The Global Service dialog box.
4
Type a Name for the category.
 
* 
NOTE: You can change the name of a service at a later date, without losing all history for a service. See Editing a Service.
5
Optional—enter text in the Short Description and Description fields. The text in the Description field appears in a dwell when you hover over a service.
6
Select a Tier. You can keep the default selection “Let Quest Foglight Decide” or optionally assign this service to a tier.
7
From the Drilldown you can select a view to drill into from this service using the service dialog box. Click Is not configured and select the view that is going to be used as the drilldown of this service.
Figure 88. An example of a custom view in the drilldown dwell.
8
In the Yes/No field, indicate whether or not the hosts of the components added to the service should be included automatically as part of the service. By default, Quest Foglight automatically adds the hosts that support any object you add to this service. If you want Quest Foglight to dynamically add and maintain the hosts for this service, click Yes. Otherwise, if you prefer to manage hosts manually, click No. You can add hosts manually by using the Add Specific Components dialog box of the Service Builder. For more information, see Adding Service Components.
9
Click Create.
The new category is added to the list.
10
Now you are ready to add components to your newly created child service. Click on the row to add the component to your new service.
A dialog box opens
11
Select one of the following options:
•
Add components to this service—select components such as hosts, servers, databases, or other services from the list of existing components. See Adding Service Components.
•
Create a child service—such as a new global or local service. See Creating a Service Contained by Another Service.
Adding a Rule-based Group of Components

Adding a rule-based group to a service allows you to manage the components monitored by a service dynamically. If a component is added or removed, the service is automatically updated to handle the addition or removal of the component from the service.

For example, if you are monitoring an application that runs four WebLogic servers, you can create a service and specify a rule to add WebLogic server instances for a particular domain so that the service is updated when more servers are added or deleted. After adding the rule, you can see that the new WebLogic servers appear automatically in the service after adding more WebLogic servers. Likewise, if the original WebLogic instances running on Windows are decommissioned, they automatically disappear from the service.

In another example, if you create a service called “FX” on the infrastructure that monitors a Web service, you can create a rule to include another infrastructure that is used for extra capacity during peak times. When the other infrastructure for high capacity is used, it shows up in the service.

A service can contain many rule-based groups.

To add a rule-based group of components:
1
In the Service Builder dashboard, expand the hierarchy and click in the Add column.
2
On the dialog box, click Add components to this service and then click Create a rule to add a group of components. Quest Foglight can auotmatically adds the hosts that support any object you add to a service.
3
The Create a rule to include a group of components dialog box appears. From here you can choose the components that you want to add and also create a new service.
Figure 89. The Create a rule to include a group of components dialog box.
4
Type a Name for the rule.
5
Choose a scope on which to run the query. For example, if you want to choose from a set of hosts, select Hosts > All Hosts to execute a query on the hosts.
6
Add filter conditions for the selected node by specifying a rule condition that is used to select items from the input. For example, in the text box, type a name-based search query such as:
name like '%.example.com'
7
Click Test and confirm that the objects are found in the query result.
Figure 90. An example of query results.
8
Click Create. At this point you should see a new rule-based group of components appear under the service that is associated with one host.
Editing a Service

By clicking the Edit button on the Service Builder dashboard, you can:

•
Rename an existing service without having to delete and recreate the service. This means that all history for a service is retained, such as the performance of the system to suit your needs. For example, if you create 50 services but then you need to change the name of the service due to a spelling error, you can change the service name without losing service data information.
•
Change the service description that is displayed when you hover over a service that is listed on a dashboard.
•
Change the tier to which a service is assigned.
•
Modify the service component relationship by adding or removing the source service and target service.
•
Change the Yes/No field to indicate if you want Quest Foglight to automatically include the hosts of the components that are added to the service.
To edit a service:
1
From the Services Builder dashboard, open the Action panel’s General tab and click Edit Service.
Figure 91. The Service Builder dashboard opens.
2
On the Service Builder dashboard, click Edit for the service you want to change.
The Edit Service Wizard opens.
3
Optional—rename your service.
4
Optional—type a description, select a tier, or configure a drilldown, and if you do not want Quest Foglight to dynamically include the hosts to be added to the service select the No option button.
5
Click Next.
From here you define relationships among services. A relationship can be visualized as a flow from one tier to another.
 
* 
NOTE: This functionality is for advanced users. Consult your Administrator if this functionality is not configured.
6
Click the Add icon, set the source and target relationship by selecting the Source Service and Target Service.
You modify the service component relationship by adding or removing the source service and target service to show relationships between tiers added to the current service. You need to add at least two services to the current service in order to configure a relationship.
Figure 92. An example of configuring a relationship.
7
Click Create.
Figure 93. The wizard dialog box displays the relationship between tiers.
8
Click Next.
9
Select the domain check boxes you want to use as associations with the service component.
10
Click Finish.
Removing a Service, Category, or Monitored Component

You can remove a service, category, or a monitored component from its related service.

To remove a service, category, monitored component, or tier:
1
From the Service Builder dashboard, click Remove for the service or monitored components that you want to remove.
2
On the dialog box, select whether you want to remove either the selected item, or the monitored components in the selected item.
 
* 
NOTE: Depending on the component that you select, a dialog box may appear or you may be prompted to confirm the deletion. Click Proceed to remove the item.
3
If you want to remove monitored components, you are prompted to select the components that you want to remove. Use Select All or Unselect All to quickly choose the components.
4
After you have selected the components, click Remove.
You are prompted to confirm the deletion.
5
Click Confirm to continue.
Associating Email Addresses with a Service

You can associate a list of email addresses with a service. Use this feature if you want Quest Foglight to send notifications to a set of email addresses about the alarms that affect one of your services.

To associate email addresses with a service:
1
On the Service Builder dashboard, click Email in the row for the service for which you want to configure email notifications.
The Mailing List Configuration dialog box appears.
2
Type the comma-separated list of email addresses.
3
Optional—click Test to send a test email to the addresses in the list.
A test email notification is sent to each address in the list.
 
* 
NOTE: Your Administrator must configure Foglight to direct outgoing mail through your mail server before you can test this functionality. Contact your Administrator if the Test button is disabled.
4
Click Save.
Email notifications are sent to each address in the list when Quest Foglight fires alarms for the service (or its components) that affect the service’s state.
 
* 
NOTE: A service might be configured to ignore certain alarms. Quest Foglight does not email notifications when they are fired.
Filtering Alarms

You can define alarm filters for any service in the Service Builder. Use alarm filters to specify alarms that are relevant to a given service as a way to keep an irrelevant alarm from falsely causing a service outage, rather than have all alarms impact the state of a service.

For example, alarm filtering can be used to ignore a certain state for a component with a high CPU usage. Quest Foglight is monitoring an application that runs on a WebLogic server and you create a service called “Retail” that includes the server and the host. The “Retail” service is shown as being unavailable when the host has a CPU usage greater than 90%. However, generally this is not considered a true service outage for this service. If you look at the host alarms, none of the alarms apply to the Retail service. As a result, you can use an alarm filter to filter out all host rules.

In another example, you can use an alarm filter to ignore the state of a service that appears as unavailable when the file system component for the D: drive fills up. Quest Foglight is monitoring an application that uses a host for the Siebel database and you want to filter out the Oracle database. The database is configured so that it uses only the C: drive, not the D: drive. A service was created to monitor the application that includes the Oracle agent and the host instance for the Oracle host. However, the service shows as unavailable if the D: drive fills up. Since the D: drive does not contribute to the availability of the application, you should add an alarm filter to exclude the monitoring of the D: drive. You can restrict the filter by choosing the FileSystem alarm, then specifying a Groovy script to refine the filter to apply only to the D: drive.

Adding an Alarm Filter

By specifying an alarm filter, you can decide what alarms impact the availability of a service.

To add an alarm filter:
1
On the navigation panel, under Homes, click Service Builder.
2
Select the service you want to create a filter for.
3
Expand the hierarchy and click Alarm Filters .
The Alarm Filters dialog box shows alarms inherited from parents by the current service.
4
You can select an existing filter from the list or click to add a new filter.
The Add Alarm Filter dialog box appears.
 
* 
NOTE: The Add Alarm Filter dialog box lists alarm rules that are applicable to all components added to the service.
5
Select one or more filtering options:
•
By Rule—select the By Rule check box and choose a rule for which its alarms are to be included or excluded. You can define more than one alarm filter for the same rule.
•
Alarms—select the types of alarms to include or exclude.
 
* 
NOTE: If both Include and Exclude filters are defined, Foglight includes alarms that are specified in the Include filters as long as they are not excluded by the Exclude filters. If only Include filters are defined, all alarms are excluded except those specified in the Include filters.If only Exclude filters are defined, all alarms are included except those specified in the Exclude filters.
•
Groovy Script—refine the filtering by running an optional groovy script. The current alarm is the only parameter passed to this script, meaning you can filter on anything that is referenced by the alarm. An example of a groovy script is: @alarm.get('topologyObject').getType().getName() == 'Windows_System_System_Table'
6
Click Create.
The filter is saved on the Alarm Filters list and the number is displayed to represent the number of filters created for the selected component.
Deleting an Alarm Filter
To delete an alarm filter:
1
Drill down to the component from the Service Builder dashboard and click Alarm Filters .
2
In the Alarm Filters dialog, select the filter and click Remove.
 
* 
IMPORTANT: Alarm filters that were added for filtering alarms fired on a component in a service, are not deleted automatically if the component is removed from the service.
Example: Filter fatal alarms fired by the Processor Utilization rule

For example, to include only alarms fired on processor 0 by the CPU_Utilization rule, you select the following parameters in the alarm filters dialog box:

•
By rule: CPU_Utilization
•
Alarms: Include All
•
Groovy script:
@alarm.get('topologyObject').get('longName') == 'Processor_Table 0')

 

Online-Only Topics

Viewing Service Details

In Quest Foglight, services are automatically monitored for availability. By default, a service is considered available if it does not have a fatal alarm.

The Service Details page provides details about the service levels that are being monitored by Quest Foglight and measuring the availability of a service. Quest Foglight automatically examines the service and calculates its current availability. Then a percentage availability is calculated and used as the basis for service level evaluation, including alarms.

Service levels are monitored in the My Services dashboard. If you select the SLA name you are able to drill down to a more detailed summary of the service level performance. The Service Levels dashboard shows availability graphs on SLA performance in the last week and last month.

To view service details:
1
On the navigation panel, under Dashboards, click Services > My Service.
The My Services dashboard opens.
2
Click at the bottom right corner of the service.
A Service Details page for certain service appears.
Figure 94. The Service Details page
3
Click Service Level Agreement to drill down to Service Level Agreement page and view details.
The Service Level Agreement page is refreshed with data about the chosen service. Use the view at the top of this dashboard to investigate the service’s compliance and availability, as well as any service level alarms that have been fired for it.
Figure 95. The Service Level Agreement page.
4
View additional information under the following headings:
•
Availability Graphs and All Monitored Components—displays availability information on SLA performance for the selected time period, as well as in the last 7 days and last month, allowing for a current versus historical comparison.
•
Components Possibly Causing Outages—if any monitored components are not in good health, a list of components that may be contributing to an outage is displayed on the right side of the Service Levels dashboard. This allows for quick action on the possible component causing the outage such as clearing the alarm.

Online-Only Topics

Customizing Quest Foglight

You customize Quest Foglight by setting a variety of user preferences that include language, the default time range you want Quest Foglight to use, home pages, and themes.

For more information, see the following topics:

•
Setting Your User Preferences
•
Understanding Page Flow Overrides
•
Setting Themes
•
Choosing a Home Page
Setting Your User Preferences

The User Preferences dashboard is under Configuration in the navigation panel. The options in this page enable you to change a number of settings in Quest Foglight. The choices you make here are saved with your user profile.

 
Table 17. The following table describes the User Preferences settings.
Setting
Description or Options

Language

This setting controls the language used in the Quest Foglight browser interface. The default is the language set in the browser.

Refresh Interval

To ensure that the views display current data, Quest Foglight automatically refreshes the pages. This setting enables you to choose the length of the interval. The default is 300 seconds.

Time Zone

Choose one of:

Server Time: the time zone used in a Quest Foglight session is determined when you log in and is the local time zone for your server.

User Time: select the User Time setting to choose another time zone.

NOTE: Requires a page reload to set value.

Time Range

This setting controls the default time range for the views. For more information, see Time Range. You can choose another interval to override the default setting of Last 4 Hours.

Working Module

Quest Foglight automatically assigns a different working module to each user. By default, the Working Module option is set to the module for your user account. If you have an Operator role, you cannot change your working module. Consult your organization’s Quest Foglight dashboard developer if you want to change working modules.

Disable Pulse on Fatal

By default, some components pulse if their state is fatal. To disable this behavior, select the Disable Pulse on Fatal check box.

Disable More option on tree nodes

By default, tree nodes with long lists of children will be shortened to show a subset of the entries, with an option to select “More”. This behavior can be disabled for all trees by selecting the “Disable More” option on tree nodes (requires sign out).

Themes

Themes are format settings that affect the look (formatted output) of dashboards and reports. The themes in the User Preferences settings are used to separately control print and remote access.You can override this setting for individual dashboard and reports using the Themes options in the action panel. For details, see Setting Themes . Specify the theme to use according to:

•
Print: refers to the default theme for the user. Use for printed views, whether through the browser (IE only) or PDF.
•
Remote: use when viewing Quest Foglight views remotely in another portal mechanism, such as SharePoint or WebLogic.

You can only change the look of your PDF reports (Create PDF) in User Preferences.
To change the theme used in generating (printing) reports to color, choose Report (Color) for the Print theme.

PDF Defaults

By default, the page size (A4 or Letter) is inferred from your locale. Use PDF Defaults to override the default setting and set the page size (such as letter, legal, or A4) and orientation (landscape or portrait) of PDFs.

Unit Defaults

By default, the temperature scale is inferred from your locale but it can be specified here.

Choose units for temperature (Celsius or Fahrenheit).

Advanced
•
Page Flow Overrides: These settings override the pre-defined links between views. For more information, see Understanding Page Flow Overrides.
•
Data Sources: These settings determine the data source that Quest Foglight uses for data and schemas.
•
Validation Exceptions: The following is an list of validation exceptions you can set:
Disable user interaction persistence: If selected, the changes made in the Quest Foglight browser interface are not kept with your user profile.
Keep all visited dashboards in cache: (requires sign out): Selected by default.
Show legacy configuration properties: Select this option if you have imported modules from a previous version of Quest Foglight and you want to see the legacy configuration properties for view components. This option is useful to dashboard developers only.
Show deprecated definitions: Deprecated definitions are not shown in the list of definitions in the Definitions Editor (including when a search is applied). Check this user preference to show deprecated definitions.
Enable preview functionality: If selected, turns on preview functionality, including making available preliminary versions of view components when creating a new view. Views based on theses components are not guaranteed to work in future releases.
Include individual scripts: To increase performance gains, many of the supporting files sent to the browser enabling the advanced functionality of the Foglight browser interface are combined and compressed before they are sent to the browser, making it difficult to debug and identify problems. Selecting this option and reloading the browser interface enables the slower, discrete files and provides more useful information in case of failure.
Understanding Page Flow Overrides

System views are linked to each other through pre-defined configurations. In some cases, you may want to link a System view to a User view instead. The Page Flow Override option enables you to make this change. Every link on the page or view indicated in the Map field that points to a target view will be redirected instead to the view indicated in the To field.

 
* 
CAUTION: This requires knowledge of how views are created, and should only be set by a dashboard designer.
Setting Themes

The Themes options allow you to control the appearance that includes the background color for Quest Foglight dashboards and reports.

Changing the Themes under Dashboards > Configuration > User Preferences has no effect on the views or dashboards displayed in the browser. The only way to change the themes for the views in the browser is to use the Action panel > General > Themes and choose a theme from the list.

 
 
Table 18. The following table describes the options.
Option
Result

Application

White background in all dashboards and views

Monitoring

Dark blue background in all dashboards and views

Report (Monochrome)

Reports are printed in black and white

Report (Color)

Reports are printed in color

 
* 
NOTE: To print PDF reports in color, the theme must be changed in the User Preferences dashboard. Go to Configuration > User Preferences and choose Report (Color) for the Print theme. See Setting Your User Preferences.
Choosing a Home Page

You can choose any dashboard to be your personal home page. Other dashboards can also be designated as home pages by a dashboard developer. These are listed under Homes in the navigation panel.

To set your personal home page:
1
Select any dashboard in the navigation panel on the left. Choose the dashboard that is most appropriate for your needs.
2
Click Make this my home page in the action panel.
The dashboard is listed under Homes in the navigation panel and is the first page displayed when logging in to Quest Foglight.

If you later choose another dashboard as your home page, it replaces the previous one.

 
* 
NOTE: You can have multiple homes. When you mark something as a home page, it becomes the default home and it is added to the list of possible homes. For example, if you add Foglight Data Management as your home page, it is added to the default set of homes for your user role, and becomes your current home. If you log out and log back in, you access the Data Management home page.

 

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation