Comments
-
Closing as this is a duplicate of Network Atlas Overhaul as pointed out by ederdal.
-
Is it any third metric added to the chart, or is there a specific metric you're wanting to add that is causing you performance trouble?
-
Monitor custom statistics based on OIDs with Universal Device Pollers
-
Sounds like you're referring to SAM's Windows Event Log Monitor which can use either WMI or RPC to monitor the Event Log on Windows machines. This would appear as a metric tile in PerfStack when you add the application containing the Windows Event Log Monitor component using the 'Add Entities' button pictured above.
-
Excellent suggestion. You can vote for this idea in the feature request forum at the link below. I also included the link for IBM LPAR/PowerVM in case others had similar requests for AIX. * Support for Solaris Zones * Support IBM Virtualization (LPar, VIO)
-
Great feedback deverts. If you aren't already participating in the NPM 12.5 beta, I'll encourage you to do so. I think you'll be pleased with the progress we've already made.
-
The Universal Device Poller fully supports tables
-
TCP Port 445 is not required for WMI, though it is used for RPC which is how SAM collects Windows Performance Counter metrics.
-
A Linux\AIX\HP-UX\Solaris\etc. agent is certainly not out of the question. Our intent is to focus the Agent on where the majority of monitoring problems exist today. SAM's agentless Linux/Unix monitoring does not suffer from many of the same problems that Windows does using RPC and WMI. WMI for instance will not traverse…
-
Sounds like you may be encountering this issue here > Unexpected website error when editing nodes in Orion Platform - SolarWinds Worldwide, LLC. Help and Support
-
Is it possible that this Citrix window embedded in the page is using Active-X and not Java?
-
Correct. Update the field in the screenshot shown above and do not modify the database directly. This change will persist through each Configuration Wizard run.
-
That is solely dependant upon ServiceNow's ability to address the issues we have identified. They have stated they are working on this now, but have not provided us with a timeframe.
-
We are currently working on adding SAML authentication to Orion which supports two-factor authentication.
-
SeUM was renamed Web Performance Monitor several years ago.
-
Can you post the installer log file so we can try and figure out why you're receiving this error?
-
Server Configuration Monitor
-
Is it possible you may have not updated your agents in a long time? It may be that the code signing certificate expiration may be preventing the agent from running. Have you tried uninstalling and reinstalling the agent to see if that resolves the issue?
-
It should be an object, not an array, since this is getting a specific team by providing the Team ID. There is a similar endpoint /alerting/teams and this one returns an array (https://docs.pingdom.com/api/#tag/Teams/paths/~1alerting~1teams/get). In short, this appears to be an error in the docs. Possibly someone did…
-
I suppose you could use SQL Profiler to capture the SQL queries against the database in a trace. Think of it as a packet capture for SQL. Alternatively, you could turn Orion logging up to debug level and parse the log files for the queries. Either of these options will be somewhat like finding a needle in a haystack if…
-
The new dashboard system is built atop an invisible grid. What you appear to be seeing is that the space between the grid is either too small or too large for the data you're wanting to display. Unfortunately, the grid is not configurable at this time. Your best option at this time likely would be to do a Top 15, or…
-
Set the status you'd like the node to have via a custom property. I'd recommend a pick list to ensure there's never an issue typos. Then configure an alert ot change the status of the node based upon the custom property value. E.G. 'f custom property 'mystatus' = 'down' then trigger alert action to change the status of the…
-
Once you have defined what the report will contain, simply use the Report Scheduler to have it sent on whatever frequency you desire.
-
You are correct. Node Management Rights are all that is required to change custom properties on a node. Aside from the generic error page that does not correctly state the exact permissions needed to access this page, is there another problem I'm not seeing here?
-
Don't fret. The information entered upon license activation essentially is only used as a last resort when the maintenance team is unable reach any of the contacts associated with the account and maintenance is nearing expiration. If this is something you're still concerned about, the only way to re-enter that information…
-
The Component Monitor wizard allows for multi-select to easily monitor multiple services at once.
-
The value you see on the Node Details is what is reported by the operating system. The value under the virtualization tab for that same node is the value reported by the hypervisor. These values are often different as the following KB article explains. https://kb.vmware.com/s/article/2031
-
That is not entirely true. SAM's Windows Scheduled Task Monitor will only monitor those tasks that reside in the root. Any tasks that you don't want monitored should be moved into a subfolder.
-
Unfortunately what you describe is not possible today in Pingdom, but can be done in AppOptics.
-
Disabled tasks should not report a failure unless their last execution failed. If you don't want certain tasked monitored by SAM's Windows Scheduled Task Monitor, you will need to move those tasks to a seperate subfolder outside of the root.