benbree

I thought of this and placed a new rule at the top of the list to send me an email on any syslog messages from the source address. Still no success. Thanks.

Yes. The syslog service is running. I tried changing to another Orion server and had the same result. Thanks for your help.

Too much monitoring on the brain....syslog messages. The kiwi server get the syslog messages just fine while the Orion syslog server does not.

Team, Adding the system to Orion did not resolve the issue. The kiwi server gets the traps just fine but the Orion syslog server does not see the syslog messages - none in the syslog viewer and no emails generated by syslog rules. Any ideas? Thanks!

Thanks for the info. I added the system - will update this message stream to let you know if it works.

Byron, Definitely approproate here! I am new to SolarWinds and Orion. What is the best way to make a suggestion and get someone to act on it? Is this the best forum for that? Thanks!

Thanks, Mindy!

Hi there, Is the ability collect the status for a group of objects part of the product yet? Any update on this? I thought this feature existed. Thanks!

The device is not discovered nor managed by Orion. It simply sends syslog messages to the Orion server running the syslog serivice. Is there a requirement for the node to be an Orion managed node to send syslog messages to Orion? Thanks.

ecklerwr1, Thanks for the response. The database and NPM reside on different servers. The database is currently about 300MB. Support seems to believe that some of my alerts are configured incorrectly and are causing database read errors. I am waiting for a call to work with the Solarwinds team to resolve this. Thanks.

One observation from our installation... We noticed that one of the MIBs we use and have written alert rules to capture traps is no longer in the database. I opened a case to get the MIB added again to the database. We incorrectly thought Orion was not sending emails for our alerts. Other may see this as well. Happy…

Hi MarieB, Thanks for following up.... We determined that there was a problem with the script we used for this and disabled it. Unsure why we got the error but decided to go another route. Thanks!

ecklerwr1, Thanks for the link. I read that one and if Orion converted Syslog messages to Orion events, this article fits perfectly. Unfortunately, the ability to specify attributes for the node is not possible using the Syslog configuration. Has anyone found a convert syslog messages to Orion events and keep source…

I have the same challenge with my servers. We did not check the interfaces on the initial discovery and now want to add the server interfaces for monitoring. It seems the only way to do this is to go to each server, list resourses, and check the interface for montiring. Would like to know if anyone has a better method or…

Update to this question...a resolution After working with support, we deteremined that there was a problem in my environment (wow - embarrassing). We changed from the fully qualified hostname for the SQL server to the IP address and magically, the connection errors disappeared. I worked with my network team the next day…

Update to this question... I worked with Solarwinds support for a few hours on this (thanks Solarwinds team!). We were able to do some database tuning and alert configuration to get Orion working (creating events and sending alarms). However, the database time out, connectivity, and exception errors continue. Anyone else…

Team, Here is an update...... It appears I have some networking issues. I started to look at the systems that were the target of the DCOM errors and found that either I could not connect to the systems or if I pinged the system, it did not return the correct address. I am working with the networking team to resolve this.…

Update - Reply from support. Team, Here is the response from support. It gives me the ability to get very close to what I needed to do. Thanks for your help! Are the Events in Question Syslog Messages that are coming into the the Syslog Viewer? If it is, you should be able to create a rule and include underMessage> Syslog…