I'm the DBA of a firm that's running Orion 8.1.0 in a dev enviroment - a virtual 64-bit sql server 2005 instance - before moving it to our prod database server. We started with MSDE, but Orion quickly outstripped the capabilities of that (at which point I became involved). We're having trouble...

My undestanding on the syslog messages is that they get dumped in the same database that Orion uses for polling. 1. Is this correct? Do the syslog messages get dumped in the same database as the polling statistics reside in? 2. Is there anyway to move the syslog database to a seperate machine and point...

I've got the Orion syslog service set to retain messages for 30 days. I'd like to keep them longer by logging to a file but I'd also like that file to be rotated daily. It looks to me like Orion can't do that. The filename field doesn't seem to support a ${Date} variable or anything...

We had some problems on our network last week which caused our DB to go from 8gig to 16gig mostly because of syslog we were keeping our syslogs for 14 days but I thought to clear out all the crap I'd reduce this down to 2 days and do a compact DB, this had the oppoiste effect and now the DB is over...

I'm required to alert on Security Event Log ID: 517 , audit log clearing events, and for some reason they are not forwarded using the event log forwarder. I verified the security log is set to be forwarded. I map a drive to to the system to create security events and I see them in the syslog viewer...

Hello, I need help setting up syslog alerts that won't flood my exchange server. Basically i have Solarwinds Event Forwarder setup on all servers to forward messages to my Solarwinds server. I want to be alerted when any STOP errors happen on any server but only notify me once but not multiple time...

Hi, Anyone got any other ideas on this, I have the same problem & have tried the suggestions above but it made no diference. Whats the best way to tell what process might be using that port? It's a pretty clean server with just solarwinds on it & the toolset. cheers, worto.

We have 4G a day dumping to syslog and the DBA's are asking when will it stop? Searched archives and said syslog purge to conform to syslos settint in ver 8.5. We are running 9, have setting down to ONE day and db is close to 100 gig now and continues. Any plans to get it working?

You can modify cisco switch configurations such that the inline power events are not logged on all or specific ports. Here's an example of how you would turn off this logging on a particular switch, for a range of ports. Example to turn off this particular logging event for range of ports on a single...