Syslog performance via the web console.

I have performance issues when accessing syslog messages from the web console. If I perform a search in the Syslog viewer it is extremly fast. However using the syslog view on the web console is painfully slow. Has anyone found a work around or way to improve this.

My database server is dedicated to only Solarwinds. It is a Windows 2k3 server running 64 bit version of Windows and 64 bit version of SQL 2005 Enterprise edition. The hardware is dual quad core xeons with 16GB of ram and an HP EVA SAN for storage. I do not this my SQL server is the issue. The syslog table in my DB is about 3.6GB for 180 days worth of Syslog messages.

Find more posts tagged with

web_console

syslog

sql_server_2005_x64

Accepted answers

All comments

bshopp

What version do you currently have installed and running?

jkennedy

We are running Orion NPM SLX ver 9.5 SP4.

bshopp

Another option to look at to distribute the load is to use our Kiwi Syslog server and you can then archive those off for your auditing purposes and then forward to Orion NPM just the critical Syslog messages. Is this something that would be feasible?

jkennedy

I don't think that is a very viable work around. I already get enough complaints from my users. It would only increase if they were required to look in two different data stores.

This is something Orion should be able to handle. We have over 100k invested in our Solarwinds infrastructure and syslog should not be this slow. There is a huge difference between the actual syslog viewer and the syslog view in the web console. I think the main problem lies in the web console.

smcdonald

I see the same performance issue with the Syslog resource on the website. The local Syslog viewer however is very fast - I dont think this is related to the database performance - my "Last XX Syslog msgs" resource on the nodes comes up instantly - seems something more related to the Main Syslog page and how it works.

Speed dropped somewhere along the road with v9 (v8 was much faster). I brought this up previously I think in another post and while chatting with support earlier this year but havn't really seen any improvements...