How to exclude Oracle tablespaces from monitoring (4308316)

How to exclude a tablespace from being monitored?

How to exclude multiple tablespaces from being monitored?

The Foglight for Oracle DB cartridge allows excluding tablespaces from being monitored the Administration page. However, when it comes to multiple tablespaces that need to be excluded, the ASP might be a slow option.

RESOLUTION 1

Use the Tablespace Settings pane to configure the default monitoring settings for the Tablespaces Storage collection, by excluding from monitoring one or more of the following types of tablespaces:

• Undo tablespaces
• Temporary tablespaces
• Read-only tablespaces
• System-Sysaux tablespaces

This pane also includes the Tablespace Exclude List section. Use this section to add one ore more tablespaces to the Exclude list.

To add tablespaces to the Exclude list:

1. Navigate to the Databases Dashboard
2. Select one or more Oracle database agents
3. Click Settings | Administration
4. Click the Collection Settings item
5. Click the Tablespace Filtering tab
6. Click Add. The Add a Tablespace to the Exclude List dialog box opens.
7. Use the Tablespace name field to enter a field name. To exclude multiple tablespaces, insert a regular expression (wild card) and select the Regex check box.
8. Click Add to complete the operation.
9. Click the Save Changes button

RESOLUTION 2 - Adding multiple (hundreds, thousands) of tablespaces to be excluded

This allows you to create a text list for a groovy script to use and add the entries to the agent property list for you per agent. It will not accept regular expressions but it will save you time from having to add these from agent properties manually.

Please use the attached DBO_update_exclude_tablespaces.groovy script. The script body contains the explanation and examples on how to use it.

Preparing the input files
Input files: prepare, for every agent, a file named <agent-name>.txt (take the exact Agent name from Agent Status which includes the list of tablespaces to exclude for that agent. Every tablespace name should be on a line of its own. Place all the input files in the same directory, of your choice.

Editing the script

Open the script for editing.

• Input file path: type the path where the input files reside in the parameter filePath
• Agent names: type the Agent/s name/s for the Agents to be update in the parameter agentNames.

Save the changes.

Running the script

The script can be executed either from the Fglam host command line, or from FMS Script Editor.

• Command line: Navigate to <Foglight_Home_Directory>/bin
• Execute fglam command line as demonstarted in the below format:
  
  fglcmd -srv <foglight_server_name> -port <port_num> -usr <username> -pwd <password> -cmd script:run -f <script_path>
  
  where <script_path> stands for the path to the current script.
• Script Editor: Navigate to the script editor in the FMS, paste the script into the editor and run it.

Notes

• when executed, the script will address the path as written in the Filepath parameter within the script.
  in that path, the script will look for a text file with the same Agent/s name as was typed in the agentNames parameter within the script.
• fglcmd executable can be retrieved from FMS_HOME/tools/fglcmd.zip

The script will have printouts ion the FMS log, when it runs successfully, or when it fails for any reason.

Log printouts

The script will have printouts in the FMS log, when it runs successfully or when it fails for any reason.

• If an agent was updated successfully, the log will print something like this:
  2011-11-16 10:38:11.515 VERBOSE [http-0.0.0.0-8080-6] script_5c26ef3e3e5c9d2838e8f7a7fc956554 Updated excluded tablespaces for agent myserver-myinstance
• If the script failed for an agent, a similar to the below printouts will show up in the log
  2011-11-16 10:38:11.515 VERBOSE [http-0.0.0.0-8080-6] script_5c26ef3e3e5c9d2838e8f7a7fc956554 - Could not update excluded tablespaces for agent agent234. Reason:
  2011-11-16 10:38:11.515 VERBOSE [http-0.0.0.0-8080-6] script_5c26ef3e3e5c9d2838e8f7a7fc956554 - java.lang.Exception: Can't read file \\myserver\c$\agent234.txt