Skip navigation

Sentry Software

9 Posts authored by: Veronique Delarue
Share This:

Monitoring multiple hosts that share the same characteristics has never been easier with Monitoring Studio!

 

The Bulk Add… feature enables you to provide a list of hosts that will automatically be independently monitored through the Monitoring Studio console:

  1. From the Monitoring Studio console, create and name a new host
  2. Click Add Bulk… and add the hostname, IP address and FDQNs (optional) of the hosts you want to monitor
  3. Click Create to save your settings

 

The new Host is automatically listed in the Monitoring Studio tree view and prefixed with Host Group to indicate that it gathers multiple hosts sharing the same configuration properties.

 

Hosts_In_Bulk.gif

 

 

See the Monitoring Studio Documentation for additional information.

Share This:

Monitoring Studio automatically detects the JRE installed on the monitored system and provides information about the JRE currently in use as well as a list of other available JREs.

You can choose to let Monitoring Studio select the appropriate JRE or force the use of an alternate one that would suit your specific requirements.

 

To manually select a specific JRE:

 

  1. Expand the Agent menu from the Monitoring Studio Web interface
  2. Select Java Settings
  3. Click the Path to the JRE field and select the JRE you want to use.

 

PATROL_Java_Path.gif

 

Note that to operate properly, Monitoring Studio X requires that Java 1.8.00 or higher and a Java Runtime Environment (JRE) are installed on the same system that runs the PATROL Agent.

 

Monitoring Studio also allows you to disable the pre-validation process to bypass the JRE compatibility check (an unsuitable JRE will prevent the solution from operating properly). You can also choose to execute the JVM as an alternate user when the PATROL Agent’s default account does not have sufficient privileges to perform the operations required by the Java Collection Hub.

 

PATROL_Java_Account.gif

Share This:

Preview and/or download the PATROL Agent log file directly from the Monitoring Studio X integrated Web interface. Messages sent to the error log include both error messages that result from a failed action, and informational messages that result from successful action.

 

Simply open the Agent > Information menu in Monitoring Studio X to get a comprehensive view of the PATROL Agent logged activity:

 

PATROL_Agent_Log.gif

 

The PATROL Agent error log records the following information for each error message:

  • the time and date of the event occurrence
  • the catalog message ID issued by the Agent
  • the message type  (I = Informational, W = Warning, E = Error), and
  • the message written to the error log.  Note that messages written to the error log are not necessarily the result of errors or failures. Some PATROL components send informational messages to the error log.

You can refresh the log and download its entire content to process the data at your convenience.

Share This:

When a Command Line or Nagios Plugin Monitor requires an additional file, such as a script file for example, you can embed it into your monitoring Template to make sure it will be distributed along with the Template configuration (through TrueSight CMA, or just with a classic configuration export).

Embedded files are text files that are saved in the Template configuration itself as a PATROL configuration variable and executed by the Monitor.

To embed a file into a Monitoring Studio X Template:

  1. Access an existing Template or create one
  2. Scroll down to the Embedded File section
  3. Click Upload File
  4. Locate and select the file to be embedded

 

Embed_File.gif

 

When the Template is used to monitor a Host, its embedded file is stored in a temporary directory. When the Monitor is run, the %{FILE:<filename>} macro is replaced with the path to the corresponding temporary file.

Nagios_Plugin.PNG

Share This:

Monitoring Studio X comes with a REST API that allows you to interact with the PATROL Agent and its main components.

 

To access the REST API, enter the following URL in your Web browser: https://<patrol-agent>:<ui-port>/swagger-ui/url=/openapi.yaml

 

Where:

     <patrol-agent> is the name of the PATROL Agent you have configured

and

    <ui-port> is the port number used by the Web UI of Monitoring Studio X

 

REST_API.gif

 

Query the PATROL to perform advanced operations or retrieve basic information about the PATROL Agent and the platform it is running on.

  1. Simply expand the function or your choice.
  2. Click the Try it out button to provide or customize some of the query.
  3. Then click Execute to launch the query. The response is conveniently displayed in the same page
Share This:

Wouldn’t it be great to visualize and interact with all events that are triggered by the PATROL Agent in a consolidated Web interface?

 

Monitoring Studio X offers a flexible and interactive way to extract valuable meaning out of events and help IT take appropriate actions, when required.

 

Discover the Event page of Monitoring Studio X

 

Events are listed in a table, always from the most recent to the oldest.

Events_1.png

 

For additional information, a detailed view is provided once you select an event from the list to allow you to change its status (Acknowledge, Close, Delete), view its entire content, copy its content to the clipboard, and add a comment to its Diary.

You can also use the Filter button to display events according to specific criteria such as their description, origin, class, types or status.

 

Events_2.png

 

Finally, the DOWNLOAD CSV button allows you can export a .csv file with the content of the list of events.

 

Enjoy!

Share This:

Save time by importing an existing monitoring template and deploy it on any Agent in a few clicks.

Your favorite monitoring templates are on Github!

To import a template

1. From the Monitoring Studio X Web interface, select the Studio menu

2. Click Import Template

Import_Template_1.png

3. Locate and double-click the template you wish to import.

Import_Template_2.png

4. The template, including all its properties, is imported and automatically listed in the Studio > Template page.

Import_Template_3.png

5. Monitoring Studio verifies that the Internal ID of the imported template is unique and prompt you to make the required changes if a problem is detected.

6. In the treeview, expand the Hosts menu and select the name of the Host to which you wish to apply template.

7. In the Templates section, enable (ON) the template to apply to the host.

Import_Template_4.png

8. Click Save.

 

The Template is ready to use on the Host.

Share This:

Have you ever experienced frustration when realizing that you spent valuable time configuring the monitoring properties for a component in your IT environment only to realize that some settings were not adequate?

 

This is where the Dry Run option comes to the rescue!

 

Monitoring Studio X provides a quick way to verify that your monitoring settings will return the expected result. Use the new Dry Run feature to challenge your monitoring settings before implementing them in your production:

 

  1. Configure the Monitoring Studio X Monitor
  2. Select the Host on which the technology to monitor is installed
  3. Click the Dry Run button.
Dry_Run.png

 

Monitoring Studio X simulates the execution of the Monitor on the specified host and displays a preview of the result right in the configuration page. You can then easily identify the potential problems and make the needed adjustments.

 

Watch the video!

 

Share This:

EMC Networker KM for PATROL constantly monitors the key areas of the backup and recovery software to ensure backups are properly performed. Any backup or restore error is instantly brought to your attention through the centralized TrueSight Operations Mgmt platform to let you take corrective actions. The solution more especially monitors:

  • Server availability: status of all the processes.
  • Log files: monitoring of the daemon.log and messages files, size, etc.
  • Pending Media Events: monitoring of the media mount requests
  • Bootstrap Messages: bootstrap settings verification, recommendations, etc.
  • Client Indexes: number of entries, utilization as a percentage and index size.
  • Devices: status of mounted volumes and history of volume mounts.
  • Save Groups and Save Sets: status, progress, size and duration

All the information collected is grouped into application classes and displayed in your  TrueSight Operations Mgmt. Alarms and warnings inform you when a suspicious behavior is detected; thus, allowing you to quickly and clearly identify peaks, troughs and trends in the performance of your backup resources before it critically impacts your business.

 

EMC NetWorker KM for PATROL 3.0.00 fully supports EMC NetWorker v9.x using the latest jobquery interface.

 

EMC NetWorker KM for PATROL 3.0.00 supports remote monitoring for NetWorker servers.

Remote monitoring is required for all servers or appliances on which no PATROL Agent can be installed. This feature is also interesting if you lack resources or time to deploy a PATROL Agent and the NetWorker KM on several servers since it allows to monitor multiple hosts from a single PATROL Agent host (see Remote Monitoring Requirements for detailed information).

 

Also, EMC NetWorker KM for PATROL 3.0.00 can monitor consecutive backups at save set level under each group client. The solution can easily be configured to monitor failed, successful or all save sets (see Configuring the Save Sets Monitoring for detailed information).

save_sets_monitoring.png

Read the complete Release Notes for further details on the improvements and bug fixes included in version 3.0.00 of EMC NetWorker KM for PATROL and download the latest version.

Filter Blog

By date:
By tag: