aLTeReGo ✭✭✭✭✭

To avoid false alarm I propose to enable retry mechanism that will try to send HTTP request once again if failure is detected: * Open "c:\Program Files (x86)\SolarWinds\Orion\APM\SolarWinds.APM.Probes.dll.config" file for edit * Find HttpClientHelperSettings element * Add RetryCount="2" attribute so element will look…

The following KB article should help resolve your issue. Unable to retrieve the PDF, CSV, or URL of scheduled reports - SolarWinds Worldwide, LLC. Help and Support

Brandon, I was only able to find one other instance of this error occurring, and it was a case opened by you for the same problem back in April. I would recommend re-opening that case with support so we can continue troubleshooting the cause of this error.

lchance, I see your case with support is closed. Hopefully you were able to get to the bottom of what was causing the issue.

Thanks Denny. I appreciate you escalating this for me.

Not at all. In fact the out of the box "Alert me when a component goes down" is a single alert that applies to any component that goes into a down state. You can further customize alerts based on custom properties, groups, IP address range, vendor, and even partial matches of names to alert upon a group of nodes or…

This issue was resolved as part of the APM 2.5 release. That was quite a while ago as we're currently on v5.0.

Agents are assigned to individual polling engines no differently than agentless polling today. You can however download the SAM 6.3 beta which includes a sneak peek at a new high availability solution for Orion which (amongst other things) provides resiliency to Agents in a similar manner to what you describe above.

The issue I believe is in how you are using groups. Groups were designed to be used for root cause analysis, dependency mapping, and alert suppression. For account restrictions, view limitations, and resource filtering you should be using custom properties.

There is currently no alert macro for the template description; only the user notes and component description fields for each individual component.

I would suggest referencing chad.every​'s many awesome examples, such as the one at the link below. Slack - Alert Integration - Node

Thanks but I was hoping to see the "Storage" category expanded. Also, once you open a case with support please post your case number here. Thanks!

For databases files that are local, but are not showing available auto grow space like the image posted above by is caused by that local volume not being monitored by Orion. My recommendation would be to list resources on that node and select the volume(s) where the database files are stored.

Hardware health for ESX servers is not collected via SNMP. It's collected using either the CIM or VMware API depending if the host is managed through a vCenter or being polled directly based on the screenshot I posted below.

Someone from our support group should be reaching out to you shortly.

Another option is to modify the web.config file located in %web_console_folder%\SolarWinds\web.config and adding the following line right after the <system.web> element. <httpRuntime maxRequestLength="1048576" executionTimeout="3600" />

The only user account that needs proper permissions is the account you're logged into the server as. If you can determine which file is locked you can find out who/what is locking the file with WhoLockMe or Unlocker. Unlocker allows you to forcibly unlock the file without rebooting the server.

The default out of the box alert "Alert me when an application goes into warning or critical state" should work to alert you whenever a failover occurs.

Have you considered rebooting the server where vCenter is installed to see if that resolves the issue polling VMware ESX/ESXi hosts through the vCenter API?

I think what would be more helpful is if you included some screenshots of how you have the custom poller defined.

The polls per second tuning tool tweaks settings inside the standard poller which APM does not rely on for polling beyond standard CPU/Memory node information. All component monitors within the APM product use the collector/business layer host for polling which are not effected by the Polls Per Second tool.

Just ensure that your virtual directory is not located in any SolarWinds path. I would recommend 'C:\inetpub\CustomHTML' or something similar. Placing your virtual directory under something like 'C:\inetpub\solarwinds' will likely result in the same issue you experienced above.

I'm running out of ideas. Is your Orion server running on a 32bit operating system by chance?

You can copy the out of the box alert and add to the trigger condition so it's more narrowly focused to that specific node or application. For example, add in the trigger condition that the node name equals the server being monitored, or better yet add the application name is equal to the name of the application template…

Many Orion HA customers utilize Load Balancers in lieu of a virtual hostname. HA is still active/passive. The Load Balancer simply watches to see which server is 'alive' (usually through health checks) and directs traffic to the active member.

The default out-of-the-box Alert "Alert me when a component goes down when" should be triggered when this occurs if that alert has not been disabled.

You can open a support case online here -> Technical Support Ticket Submission Form | SolarWinds

The only 'changes' made are the addition of a record created based upon the values you entered in the BIND step. To create a virtual hostname we need to know what you want that hostname to be. Let's say we call it 'orion'. Next, we need to know what zone to create that record, in the event the DNS server services multiple…

tigger2 wrote: The only method supported today is to use a "virtual hostname" which is a DNS CNAME/Alias record (I don't know the record type). In a multi-subnet failover configuration a virtual hostname is optional and provided as a convenience feature. Some customers opt to use alternative means of directing traffic to…

In NTA's next release, they are moving back to MSSQL, but it will require MSSQL 2016 or later. SQL 2014 will not be supported, as it requires features only available in SQL 2016. If you're not running SQL 2016, no worries. You can stay where you are with FastBit and still upgrade to the next NPM, NCM, and other module…