aLTeReGo ✭✭✭✭✭

Sorry for the bad link. I can't seem to find one that specifies Orion and not Toolset, though their implementations are essentially identical. On a status poll Orion performs an ICMP ping operation. If that ping fails then we set the Node to Warning Status and begin Fast Poll. By default, we will poll in Fast Poll mode for…

I think it would be better to engage SolarWinds sales and speak directly with a Sales Engineer who will be able to walk you through Orion deployment architectures and discuss scalability limits. I will state that SAM components do not count against element scale. You could for instance, monitor 100,000 elements and 150,000…

I see the issue now. Each Oracle User Experience Monitor supports a single statistical and one optional message "string" value. Your query cannot return an entire table of data and have that represented in any meaningful fashion within SAM.

Agents have their own status separate from Node status, since not all agents are nodes. Below is an example of some of the alerting properties for the agent.

Ahh, now I see the APMTEST and APMTEST2 profiles. I deleted them both and now I'm getting the error Testing on node <NODE NAME>: failed with 'NotAvailable' status Unable to locate MAPI user profile It did recreate the APMTEST profile, but it's still not working.

I've taken the liberty of turning Petr.Vilem's code into a Report Writer report and posted it to the Thwack content exchange. It can be downloaded from the link below.

Is the Windows Firewall enabled by chance? Are all components in this template unknown or "Down" or just some? If it's just some, which ones are in a down or unknown state? Has this template ever worked against this node? Did it just stop working after the upgrade? Has it not worked since upgrading or does it occasionally…

It sounds like Lexmark is using enumeration, so what's actually occurring is that the device is returning "1" but the MIB file interprets that as being noTonerError. You should be able to confirm this by doing a MIB walk of the device and searching for 1.3.6.1.4.1.641.2.1.3.1.6.0. I did a quick Google search and was able…

"Messages Queued for Submission' is not a metric available when monitoring Exchange 2013. This is metric is only available when monitoring Exchange 2010 in AppInsight for Exchange. These transport metrics are however available in the following application template. * Exchange 2013 Mailbox Role Counters (Advanced)

I believe the property you're looking for in your Trigger Condition is not "Status", bur "Numeric Status" or "Rate".

The following thread is where we track device identification via SysOID and update them accordingly with each major release. Tell us your "Unknown" devices!

Ahh, much better. Thanks again Tim!

While you can call Curl from a PowerShell script you will need the PowerShell to pass the resulting output along with a proper exit code for the monitor to work with SAM's PowerShell script monitor. This is what I meant above by creating a VBScript or PowerShell wrapper for your Curl code.

You can also find working examples here > marketplaces/azure/npm/templates at master · solarwinds/marketplaces · GitHub

Also, have you clicked the "test" button after enabling the debug logging? The debugging will occur during the next poll. So you can either wait for it to occur naturally or force a poll using the Test (in the template editor) or Poll Now button on the Application Details view.

Terrific. That worked like a charm. Thanks!

jmorse, you are correct. I had to set this up in my lab to verify but it would appear that it's not possible to select the individual statistic values for multi-value scripts in the multi-object chart resource. You can however use the Custom Object Resource to display the status of multi-value scripts on your summary page…

If the errors are happening consistently every 21 seconds (or so) perpetually without end, then it's very unlikely this is caused by Orion. If you can imagine an application template assigned to a node that contains say 5 WMI based component monitors that's configured to poll once every five minutes (default behavior),…

At this point in time I would recommend against the use of this template "Exchange 2010 Database Availability Group. The functionality this template provided has been superseded and greatly enhanced in the SAM 6.1.x release with the introduction of AppInsight for Exchange. SAM 6.1.x is available now for download through…

The image you posted is not visible to anyone other than you. It appears to be linked to your Office365 account.

Keep in mind that as AppStack matures over time additional categories can and will be added as future versions are released. It is very unlikely that any customizations made directly via the SQL database will be preserved as a result, so keep that in mind as you hack your way through the database. As always, ensure that…

You can manually repair the Job Engine database by following the steps outlined in the KB article listed below. * SolarWinds Knowledge Base :: Replacing a Job Engine Database

I'm no Glassfish expert, but to my knowledge it does not support SNMPv3. Your options would be to change the SNMP configuration of the node to use SNMPv2 instead to mirror glassfish, or monitor the Glassfish server using JMX rather than SNMP.

The "SMTP Monitor" in the "Microsoft IIS SMTP Server" template is a simple TCP Port 25 Check to verify that port is listening properly. This should operate without issue on an Agent managed node without any need for the Orion server itself to be able to communication over TCP Port 25 with the endpoint. That's the job of…

Thanks. Please keep us updated on your progress.

If you're simply trying to include the full event log message text within the alert, why not use the ${WindowsEventMessages} macro instead?

This case is being tracked under NS507977

Forgive me for not reading closer. It appears your Custom Property was never created properly since it's throwing an exception. The reason why however completely eludes me. I would suggest opening a case with support so we can look through your diagnostics and determine the cause of the issue.

Thanks for sharing . We'll look into this and document it accordingly.

Anything you see here you should have in NPM 12.5 or later without the need for SAM.