Having the ability to filter out low level events (Levels 4-7) at the agent level before sending to Log Analyzer and not count against the 1,000 messages per second at the Orion Platform level. Increased EPS threshold for LA...
Is there an option to save syslog/trap messages to a file, using Log Analyzer/Viewer custom rules? I am thinking of similar functionality to older Syslog Viewer: https://support.solarwinds.com/SuccessCenter/s/article/Save-Syslog-messages-to-time-stamped-files?language=en_US The only option I found is to forward syslog/trap…
Orion generates a multitude of log files in various directories which can be difficult to decipher and manage. I'd like to leverage Log Manager for Orion to aggregate these logs, parse them and ultimately reduce the time it takes to identify and remediate issues with my Orion installation.
Log Manager for Orion comes in two flavors. 1. A free basic edition that provides basic syslog and trap monitoring that will cover most of the existing functionality with the legacy Syslog and Trap Views that were included with NPM. 2. An enhanced edition supporting charting, live-mode, tagging/filtering, event, alert…
One more for the LA team, how about auto refresh when you apply a filter or two. I am currently filtering on a device, APC for instance. If I stay in the page, the refresh does not update the data on the page. Adding a second filter, like error or hostname should also allow me to view updated info. If not, add a refresh…
There are only 1,000 log events that are viewable in Orion Log Viewer.
Hi all, Currently any users in the environment who need to perform VNQM duties do not have the access to do so unless they are an administrator. This creates issues from a security perspective and a liability as there are users who have no interest in being administrators but need to perform VNQM duties in SolarWinds.…
Problem: Log Analyzer cannot create alerts for each individual "instance". An option to use a varbind as a "discriminator" would allow for unique alerts per instance, and also for resets to apply to that instance only. Examples of instances that might generate alerts are BGP neighbors, EIGRP neighbors, Cisco FRUs,…
Currently the only way to edit what Windows Events are collected by Log Analyzer is to edit a custom query within the advanced configuration. Would like to see this in a more user friendly format. An article on how to do the edits manually can be found here but the process could be simpler. How to Filter Windows Events…
recently I come to know that there is no feature available to set wait time under OLV/LA before forwarding trap. Why we need this wait time: * As there is no control on trap that is if any single trap we received that directly forwarded to create ticket/incident. * With help of this option we can avoid flood of…
It looks like you're new here. Sign in or register to get started.