aLTeReGo ✭✭✭✭✭

I'm also running 2020.2.5 and am unable to reproduce this issue. &#183 is the code for the 'middle dot' character. This is what is used to separate the interface name from the description when a custom description is used. See below for the comparison of the dash vs. dot for default vs. custom interface descriptions. I…

What version of the Orion Platform are you currently running? Note that if you simply wish to use this same widget type on the same dashboard, you can simply cloan it and then modify that copy. 

Can you copy/paste the interface description on the device as seen through the CLI/SSH?

You could integrate Orion with an alert aggregation and management service that provides a mobile app. Below are a few with direct integrations into Orion. * PagerDuty * xMatters * Opsgenie * AlertOps * VictorOps * PagerTree * iLert

Have you verified all of the items for reverting Log Viewer back to legacy Syslog & Traps have been done and are set appropriately? It's possible that one or more of these could have somehow been undone by the recent upgrade. https://documentation.solarwinds.com/en/success_center/la/content/lm/lm-uninstall-lm.htm

If the node is reporting 'down' using Agent-based status polling but can still be 'pinged' from the poller it's monitored by, then it's possibly an issue with the Agent or the AMS. For example, if you stop the Agent service running on the endpoint, this will cause the same behavior. Similarly, if the OS locks up, you would…

Are you using the legacy Syslog & Traps, or are you using Log Viewer (the free version of Log Analyzer)? What is the URL you're going to that produced that error? Please paste it here without the server name/IP. Just need to know what comes after that. E.G. /orion/.....

How availability (up/down status) and response time are calculated does not differ depending upon which method is used (ICMP or Agent). The only difference is which protocol is used. In a lot of environments where the Agent is deployed, it's not possible to 'ping' the monitored node from the Poller it's managed by. Either…

The following Report may be what you're looking for https://thwack.solarwinds.com/t5/-/-/ta-p/518105 These others you may also find useful AppInsight for SQL Credential Inheritance Report APM Component Monitors Whose Credentials are not Inherited from the Original Template Credentials Used By APM Component Monitors

WIthout some of the information above these log entries, it's impossible to ascertain why the installation failed. Since this is a trial, I would recommend contacting Sales. They will be able to line up a Sales Engineer to get you past this issue. Sales Contact Info Americas Phone: +1-866-530-8100 Phone: +1-512-682-9300…

Application templates can be programmatically defined using the Orion SDK. https://github.com/solarwinds/OrionSDK/blob/master/Samples/PowerShell/SAM.Application.ps1

From the Agent Management page in Orion, is this Agent reporting that the Agent itself or any of its associated plugins are in need of an update? Note that when you upgrade the agent itself manually, the plugins are still updated from the Orion server. This is because we only deploy/install plugins that are actually used…

I would recommend replacing the ${NodeDetailsURL} macro with ${N=SwisEntity;M=DetailsUrl}

I was able to reproduce this issue in my lab running 2020.2.5 and have logged it as a bug. We are tracking this internally under CORE-17402.

Dynamic Application template assignment is handled through groups. Define a dynamic group based upon whatever parameters you wish, then assign the appropriate application template to the group, rather than the node itself. Any nodes which meet the criteria of the dynamic group will have that application template assigned…

This can be accomplished using the Orion SDK. There are several examples using a variety of different languages. Below is just one using PowerShell to run a discovery against a WMI node and import the results to begin monitoring. https://github.com/solarwinds/OrionSDK/blob/master/Samples/PowerShell/DiscoverWmiNode.ps1…

It's my guess that the shared mailbox does not support external emails. You should be able to troubleshoot this outside of Orion using Thunderbird and the same SMTP server settings defined in Orion. 

The node' memory usage show in the radial gauge is showing actual Memory Used, excluding cache memory. Because this is a volatile cache that is used dynamically and surrendered when applications need that additional memory to function properly, most people would not consider that to be 'used'. At least not in the sense…

Alerting uses the same values displayed within the Orion web interface for that node. 

Your use of PowerShell scripts to query a database I imagine would not be FIPS compliant as the encryption algorithms used are likely the same as SAM's ODBC User Experience Monitors, since both presumably rely upon the same ODBC drivers. If you're working around FIPS limitations with non-FIPS compliant methods, then why…

Run WindowsUpdate and apply all available updates to the system. Note this may require you to run WindowsUpdate multiple times, rebooting when asked. After each reboot, re-run WindowsUpdate until it says there are no new updates available. 

Some tools consider items such as cache to be used memory. This is how NET-SNMP calculates memory used, and this is not typically what most people would consider to be accurate. That is because the Linux operating system will use any/all available memory for disk cache until such time as it is needed for an application.…

Various Linux tools display values differently, such as ps, top, glances, htop, etc. etc. All of these tools however gather their information from the same place. That bing '(/proc/meminfo)'. If you 'cat' this file you should see all memory metrics available for that machine and their most current values. MemTotal:…

You are correct that this error can occur when pre-staging. In some very rare situations for unknown reasons, the upgrade of the Administration Service can fail, resulting in this error. If you or anyone else encounters this issue, please generate a diagnostic and open a support case so that our development team can…

You are correct. If this is not a viable workaround, your best option may be to continue using Network Atlas for these types of maps until Wireless APs are supported by Orion Maps.

When running the offline installer you should be presented with two options. Upgrade Now, or Pre-Stage Installation Files. [View:https://content.screencast.com/users/zmq503o1/folders/Snagit/media/6291d145-e93a-460d-a536-757d1be00347/Offline%20Installer.png:320:240] The message you are receiving does not make sense for…

If these are hosted by IIS, I would recommend verifying the NTFS file permissions are the same. 

One option to consider is to add the APs as ICMP nodes to Orion. This would allow you to add them to Orion maps. 

The Linux Agent polls memory statistics from the /proc filesystem (/proc/meminfo) as follows: ValueCapacityUsedPhysical MemoryMemTotalMemTotal-MemFreeVirtual MemoryMemTotal+SwapTotal(MemTotal+SwapTotal) - (MemFree+SwapFree)Swap SpaceSwapTotalSwapTotal-SwapFreeShared MemoryShmemShmemCached MemoryCachedCached

Which Orion modules are you currently using?