aLTeReGo ✭✭✭✭✭

So the Asset Tag information is manually entered into BIOS to match a sticker placed on the machine by your organization to track the asset. Is that correct?

We did have a Thwack community member post a PowerShell script that does something Similar but SAM 5.0 included the SSL Certificate Expiration Component Monitor which is not dependent on PowerShell. You can download the template posted to Thwack which utilized this component monitor type and assign it to your nodes…

It would seem there is something amiss with the WBEM Providers installed on that server. I would recommend you start by uninstalling them completely and re-installing. It's far more common for SNMP not to work then WMI but it does happen on occasion. In these circumstances uninstall/reinstall usually fixes it, but in more…

This exists today using Baseline Macro Formulas, as outlined in the Administrators Guide at the link below. * Baseline Threshold Macros

These are fair asks, but I think this reads a bit like solutionizing and could benefit from a detailed description of the pain point you're experiencing that these changes are aimed at addressing. While I can make some basic assumptions, I could be mistaken, while others reading this may not be able to fully appreciate how…

From the ReadMe.txt included with the hotfix "fixes an issue where HTTP Monitor, HTTPS Monitor, Form Login Monitor, and Web Link Monitor may convert URLs to lowercase characters which can cause false Down statuses and HTTP 404 errors if the web server is case sensitive."

Windows Server 2008 R2 is no longer supported by Microsoft. It is in extended support only. This means that fixes for issues are no longer forthcoming, only paid technical support. This does not mean that you cannot continue to run SAM 6.4 or NPM 12.1 on Server 2008 R2 for the full duration of their supported lifecycle…

Agreed, but these OS's are not binary compatible with Linux. For this reason I felt it important to break them up in the likely event we are unable to deliver on all Linux and Unix flavors in the first release, we can use the information to help us decide in what order to release these other non-Linux agents.

Hotfix 5 is currently out as of the time of this writing.

jeremymayfield​, I believe what you are referring to were contests in the past where the ideation forums were used for voting for the 'best of' something. If memory serves, DanielleH​ did not want others downvoting others submissions to skew the results in their favor. That's a fair rule for contests, but it should never…

It's recommended that you monitor the cluster VIP as a node in Orion and monitored shared disks through that VIP rather than via the individual cluster members. This would ensure the volumes are always monitored, regardless of which member of the cluster is active.

No. Unfortunately Microsoft does not expose this information via SNMP.

You could just add the following entries to the hosts file on the machine where the player is running. 127.0.0.1 google-analytics.com 127.0.0.1 ssl.google-analytics.com 127.0.0.1 www.google-analytics.l.google.com

mxr662 wrote: The upgrade has caused our system to be very unstable. Support keeps telling us to wait for a patch, but support is unable to contact the developers to find out when said patch is available. We replaced a dll file from the buddy drop, but it did not help. What is the stability issue you're having? Do you have…

Since the clock rolls back one hour it would make sense that there are 12 more values for the same hour, since that hour essentially occurred twice. I would not expect a gap in data unless the clock rolled forward an hour, since that hour never actually occurred.

SAM 6.3 Beta 2 is now available which includes a Linux Agent for Node, Volume, Interface, and Application monitoring. If you already own Server & Application Monitor and are under active maintenance, you can sign-up to participate in the beta at the link below. * https://thwack.solarwinds.com/thwack-beta.jspa?groupID=1003

AppInsight for Exchange supports Exchange 2016 in version 6.2.4.

Changing polling methods between Agent and WMI should preserve both history and monitoring selection in SAM 6.3 currently in beta.

Yes this is logged as a feature request and being tracked internally under FB306223.

You need to populate the Custom Property value with a hyper link, rather than a URL. Example below. <a href="https://www.google.com">Google Search</a>

What kind of information would you expect to see in an "AppInsight for .NET"?

RabbitMQ templates are available at the links below: * RabbitMQ (Linux and Unix) * RabbitMQ (Windows)

I don't like to quote Amazon pricing but they do make it available publicly here -> Amazon EC2 Pricing For what you're describing you wouldn't need anymore than a small instance. If you only needed this temporarily then you could use an on-demand instance. I recommend this for testing/evaluating. If you plan to run this…

If you currently own SAM you can simply sign-up here. You will then receive an email shortly thereafter containing a link where you can download the latest SAM beta.

This functionality will be controlled similar to how the Real-Time Process Explorer is today, where users will be required to have a specific Orion permission enabled on their user account to stop/start/restart services from within the SAM web console.

chisle​, what version of Orion Platform are you currently running, and have you opened a support case regarding this issue?

Webhooks can be used to trigger actions/verbs in Orion, such as acknowledging an alert or even add notes to an alert, but there is no way to input data (metrics or log events) into Orion like you can for AppOptics or Loggly. 

Can you post the file here? It's possible that this is an improperly formatted file.

More granular permissions for remediation actions is a good feature request, and one I'm tracking internally under FB196255. In the meantime however, newly created users or groups, as well as existing users and groups who did not have the "Orion Admin" permission do not inherit these privileges automatically. They must be…

[Settings -> All Settings -> Manage Hardware Sensors]