aLTeReGo ✭✭✭✭✭

SAM 6.0 (Currently in beta) does not include support for IBM Blade Centers. If you have MIB walks taken from these devices using this tool, please post them here. If you prefer to email those MIB walks you will also find my email address in that thread.

What information specifically appears to be missing from hardware health via WMI that is available via SNMP for your HP server? Have you installed the latest version of the HP Insight Management Agent, including the latest version of the WBEM providers that are required for WMI polling? * Drivers & software for HP ProLiant…

I concur. That would be better.

Indeed it has. This is available in the SAM 6.3 beta.

Can you confirm the NTA MSI is located under 'c:\ProgramData\Solarwinds\installers' directory.

This is not related to Network Sonar discovery. This is specific to background discovery, which is something we use on occasion when releasing new free features and enhancements to make adoption of them easier. Another example of where you might have seen this was with APC UPS monitoring in the 2018.2 release.

The agent should continue to operate with reduced functionality in compatibility mode. The reduced functionality means that you may not be able to take advantage of any new functionality provided by modules you own which rely upon the Agent. Core features and functionality though, such as CPU, Memory, response time, etc.…

Thanks everyone for your feedback. I think we all understand the use cases associated with this product idea. We've captured this as a feature request and logged it under under FB196329.

Documentation for a new release typically isn't available until GA. On occasion rough drafts are made available during the Release Candidate. I will however see about getting an early draft version sent to you via email.

Could you post a sanitized screenshot of what this looks like in the SQL 2012 Management Studio so others know exactly what you're referring to?

Orion Log Viewer does utilize a seperate database, but the same database server. It provides a lot of advantages over Orion's legacy Syslog & Trap receivers. Most notably, it's all managed through the Orion web interface, and uses the same web based Alert Manager as the rest of Orion.

Have you tried PerfStack in the latest release? PerfStack shows data based upon your browser's timezone automatically.

How do you see credentials working within groups? Would you rely solely upon credentials embedded within the application template itself, or would you imagine assigning credential to a group somehow? I'd mention node credentials for nodes that are managed via WMI but there are a great number of templates this wouldn't work…

The AppStack Environment resource can be added to any Summary View. Once done, you can customize the layout settings for that resource by referencing it under the "Layout Settings" on the "Environment" view. Filter the layout, choose your settings, then save the changes to that layout. When you return to the view where…

I would sooner recommend using an application custom property instead, but currently neither are supported when used with a Windows Performance Counter component.

You are correct. Due to certain SWIS requirements, both hosts must have the same host name.

I don't believe this is a feature request, but rather an issue. My recommendation would be to post this question in the Server & Application Monitor​ forum.

You are a hotfix or two behind. Server 2019 support was added in one of the most recent hotfixes.

Is the node managed via WMI? Have you enabled AppInsight for Exchange using "List Resources"? Ensure that you haven't manually assigned AppInsight for Exchange to the node.

This is something we're currently working on.

Have you tried flushing your browser cache and/or a different browser? If you open developer tools in your browser and refresh the page, do you see any errors?

Cool. Once you upgrade to 2018.2 and SAM 6.6.1 you should find this issue is resolved.

I'm not having difficulty adding a Custom Chart resource to a view using SQL. See screenshot below. Am I missing something?

The error you describe could occur for a variety of reasons. E.G. The SolarWinds Information Service failed to start for some reason. Support should help you identify the cause. This could also be a licensing issue. Regardless of the reason, this is hardly the only way to migrate your Orion to a new server. It's the only…

Both Node and Application Custom Properties are available for use in script monitors with SAM 6.0.

I don't have an exhaustive list as background discovery runs only once after upgrade, presuming there is anything new in that release that warrants its usage.

This is already possible today using the "External" node type. That is the primary reason why the "External" node type exists. For additional functionality however you may want to consider using Web Performance Monitor (WPM) instead.

When Orion initially configures IIS it is bound to all IP addresses on the server. If there have been modifications to the bindings (not uncommon when moving to HTTPS) then you will need to adjust those bindings appropriately to allow IIS access from the VIP. Nice catch matnetmin​!

I think this may be what you are looking for.

Hmm.. I see what you mean. I've logged this as a bug which is being tracked internally under CORE-1070. Please open a support case so we can provide you with a fix as soon as it's available.