Comments
-
Yes, you can choose to stay on the legacy syslog tool if you want. There is a screen during installation that will give you the option to go with the new log viewer or retain legacy for now. For the spoofing question I am validating with the engineering team but I believe we now default to always spoof if you are…
-
Yes, it is the same maintenance... You can see the DB Maintenance logs swdebugMaintenance.log from following location: C:\ProgramData\Solarwinds\Logs\Orion
-
Yes there is maintenance that occurs on the logs database. However, if your environment is generating anything close to the 1000 events per second that we can ingest, 360 GB would be about right for 5 days of retention... Per the system requirements you will see roughly 100 - 130 GB / Day. LA 2019.4 System Requirements
-
Yes, you can still create rules to forward a given message to another location if you need to.
-
I sent you a private message to set up some times to discuss.
-
The LA DB is separate from the Orion DB so yes you could easily put it on another VM / SQL instance if you like but it can also live in the same instance as the Orion DB too. Yes, LA can forward logs to other systems and Orion has native integrations to Service Now and Solarwinds Service Desk Log forwarding Orion Platform…
-
Orion Log Viewer / Log Analyzer can handle 1000 Events per second or about 90 million events per day which is significantly more than Kiwi. However, some people do still use Kiwi as a sort of front end to process and discard events and only send along specific message to Orion for further action. It is really just about…
-
Authentication improvements along with certs and proxy support are part of what we are currently working on: WHAT WE'RE WORKING ON FOR WPM (Updated Nov 13, 2019)
-
Hi k1gaudineer sorry for the late reply here. For some reason I missed this when it initially posted. We are actually doing some research in to use cases where timeouts occur during a search and it sounds like you have some of those. I would like to speak to you about those as well as get some deeper input from you on the…
-
Yes, that is correct. We will support both recorders for the foreseeable future.
-
It depends on what you mean by standalone. Orion Log Viewer is an add on that requires at least one of the following modules: NPM, NCM, SAM, VMAN or UDT. However there is a more feature rich paid version Log Analyzer that can be installed as a standalone instance if you want. The nodes you want to collect logs from do have…
-
Based on feedback from the beta test cycle and feedback sessions with customers we found that the new recorder reached a functional milestone that was important to put in the hands of all users for production use. We made the decision to ship the new recorder now but continue to include and support the old recorder until…
-
Thanks for the input JD... Very useful and as serena mentioned we are looking at application logs as a possible next step for Log Analyzer so I may ping you offline for some additional detail.
-
Great! Glad to help! Let me know if there is anything else
-
The first screen shot is where you should be looking. That being said, I am trying to piece this together as something doesn't make sense. You said you are only using the basic Log Viewer (you do not have an active license of Log Analyzer) Windows Events are only supported in Log Analyzer LA feature comparison so it is odd…
-
OLV can certainly run on the same Orion instance as SAM along with any other Orion modules you have. Collection of flat log files is not supported in the current release but it is something we are considering for possible future releases.
-
martian monster We are in the process of reorganizing the documentation to more clearly differentiate Orion Log Viewer from Log Analyzer. Give me just a bit to check on the progress of that effort and I'll ping you. In the meantime is there a short list of things you are trying to do that I could try and point you in the…
-
Love this! I frequently have folks ask for a quick primer on how to use the custom script monitors in SAM... Now I can send them this article!
-
For those who may have missed it elsewhere, WPM 2019.4 is now generally available. Web Performance Monitor (WPM) 2019.4 Is Now Generally Available
-
The latest beta is available now! Join us in the beta forum: https://thwack.solarwinds.com/thwack-beta.jspa?groupID=1492
-
For those who may have missed it elsewhere, WPM 3.0 is now generally available. WPM 3.0 IS GENERALLY AVAILABLE!
-
I am checking on this with the team. Not sure if there is any info in the logs or if we need some SQL / SWQL to solve this.
-
Hi Thomas, We are in the process of drawing Beta 1 to a close. We received lots of excellent feedback and we have been continuing forward with development. Good progress is being made. While we cannot comment on specific dates, as we get closer to a release candidate, we will be reaching out to folks to recruit their…
-
For those who might be interested, the first beta for WPM 3.0 is now available: https://thwack.solarwinds.com/thwack-beta.jspa?groupID=1492
-
Have you tried cycling the WPM Player services on the location?
-
This line sticks out: time="2018-12-04T19:15:00Z" level=warning msg="There is no valid SAM or VIM license. Polling is skipped." Just to clarify the obvious... You do have a valid SAM or VMAN license applied to this Orion instance, correct?
-
You could do a couple things... One would be to add a custom resource to a page and use a filter to only show certain resources on certain nodes (screen shots below) You may also want to consider looking at Custom Properties to do more logical groupings on your devices. Create a custom property Click Customize Page in the…
-
That is not possible in the product today. You may want to create a feature request so we can track that and consider it for a future release as well as gauge the interest in such a feature from other customers: Web Performance Monitor (formerly SeUM) Feature Requests
-
You may want to look at using Custom Properties to do the logical grouping here. In my experience when it comes to alerting, Custom Properties are easier to use and a little more flexible. Create a custom property
-
If the node in question has a web based GUI you can enter the URL or IP for that here and then you will be able to click on a link in the node details page taking you directly to the GUI. Basically just a time saver when you need to hop between the monitoring interface in Orion and the actual GUI on the node.