aLTeReGo ✭✭✭✭✭

This may not be an out-of-the-box metric included within one of our templates, but it's a relatively simple process to monitor it (or any other counter) using the Component Monitor Wizard located under [Settings -> SAM Settings -> Component Monitor Wizard -> Windows Performance Counter Monitor] as shown below.

Most definitely, but you'll need to give us more background on your alert configuration. It does sound as though that you'd probably be much better off using Custom Properties in this situation rather than Groups.

How is the node identified in Orion? E.G. What's the vendor type? A screenshot of the 'Node Details' resource for the node where this option isn't available would be very helpful.

You should upgrade to Orion NPM 9.5.1 and check out this thread here

Probably the best place to start would be to create a new Application Template for these applications. APM does include a wizard for creating new application templates or adding component monitors to existing template for the most common types of component monitors. This wizard can be found under <Settings -> APM Settings…

Your issue is likely the misuse of alert suppression conditions. The Alert Suppression tab isn't for filtering alerts as you've done here, but is rather to define a condition that can't also exist in the same context as the trigger condition. It's used primarily for dependency alerting. E.G. Trigger Condition: Alert me…

The error message you're receiving is normal given that "Q$" is not a directory but a share. An alternative method that will provide you similar information about the volume is to use the Windows performance counter information for the logical disks. Screenshots provided below.

Are you sure you created a custom property using the Win32 custom property editor or did you simply create a dynamic group through the webui? Groups are primarily used for dependency relationships where custom properties are used for organization and hierarchy structuring. It would also be helpful if you provided a…

We have several customers using the Web Performance Monitor remote player for this very purpose.

I would recommend against disabling automatic agent updating as previous versions are not compatible with the latest. Those agents will essentially be in a non-functional state until such time as they are updated to support the new version of Orion. Updating those agents would then be a tedious manual process. As a general…

Acknowledging the alert, either through the web console, or through the acknowledgement URL macro that can be used in Email and SMS alerts in the Advanced Alert Manager will suppress any further escalation.

Spaces in HTML are represented as '%20'. Alternatively you can normally wrap file paths in quotes when those paths contain spaces. I would recommend trying both methods and see which works best for you.

No the ability to view chart/graph data in System Manager has not been removed from Orion NPM v10.0 SP1. I just looked on my server and mine is behaving normally. Does this happen on any/all graphs for CPU/Volumes/Interfaces?

The statistic value must be numeric. The value "ok" is likely what's causing the status to be returned unknown. Change "Write-Host "Statistic: OK";" to "Write-Host "Statistic: 0"; and you should return an "up" status. Select-String -Simple OK c:\log.txt Write-Host "Statistic: 0"; Write-Host "Message: Registered"; Exit 0;

You are correct that this alert will fire either when the application is in a warning or critical state, but if the trigger condition does not change it will not re-fire. The work around is to define two separate alerts. One for warning, and another for critical if you need to be re-notified when the level is escalated.…

This is precisely what the MAPI User Experience Monitor is for. While this hasn't been added to any specific template, you can add it easily to any of your existing templates or create a new template and include this component monitor. More information on the MAPI User Experience component monitor can be found at the link…

SAM's HTTP & HTTPS Monitors do allow for Restful API queries

Hmm... Indeed this option appears to be missing for reasons I cannot explain. I even tried exporting, deleting, and re-importing and that didn't seem to make a difference. I'll log this as a bug. In the meantime I suggest using the ${USE_BASELINE} macro for now until we can get an updated version of the template posted…

You probably have to re-list the resources for that node in the system manager and re-select the network interface and delete the old network interface. I've see this a few times after updating Intel network drivers on my Windows Servers. No need to delete the entire node, but the OID that identifies the network interface…

Unfortunately this information is not available via the Report Writer. This is a bug we are tracking internally under FB369581.

It may be that the network service name is not properly configured in the SAM component monitor

You can simply apply the HTTP User Experience Monitor to any managed node in Orion. If the node is external you can add a new external node and apply the HTTP User Experience Monitor to it. Node status isn't monitored for external nodes, only the applications assigned to them. Another option would be to take a look at our…

Have you tried monitoring the Bluearc NAS directly via SNMP? If it supports the Host Resources MIB these volumes should be monitorable no differently than Windows or Linux/Unix volumes in Orion.

This has been discussed previously in the following thread. IBM z/OS Monitoring

Absolutely. You can select multiple ICMP nodes under "Manage Nodes", click "Edit Properties", check the "Polling Method" option, provide the SNMP community string, and submit your changes and that should be it.

Hardware Health Monitoring of Servers is a function of SAM, not NPM. You may have greater success posting this question to the forum. In the meantime, I recommend upgrading to SAM 5.2 SP1 to see if this resolves your issue.

No useful monitoring information is available for MySQL 4.1 via ODBC. This functionality wasn't added to MySQL until v5.1. You could theoretically gather some information using script monitors through the MySQL command line utilities but it would probably be easier to just upgrade to MySQL 5.1. There are two other threads…

The response time metric returned by this component is measured in milliseconds.

Instead of unmanaging the interfaces you might want to consider reducing the interface polling interval for those device interfaces instead. Polling them once every 15,30, or even 60 minutes would be more beneficial than simply unmanaging them. 

You only need to configure one alert to receive a notification of an application going up or down. The alert you receive when the application goes down is handled through the "Trigger Actions" tab of the alert, while the alert you receive when the application comes back up is controlled through the "Reset Actions" tab.