nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Rules Limitations & Performance

byrona

I was curious if there is any limitations on the number of rules you can have in Kiwi and if there are any noticeable performance issues when you have a lot of rules in Kiwi?

Find more posts tagged with

Accepted answers

mark_wiggans

hope this helps...

http://www.kiwisyslog.com/help/syslog/index.html?rules_maximumrulecount.htm

All comments

mark_wiggans

hope this helps...

http://www.kiwisyslog.com/help/syslog/index.html?rules_maximumrulecount.htm

byrona

That is what I needed though I have a few follow-up questions based on that document...

The Auto-Split feature sounds like it's just applicable for determining where logs will be stored and isn't applicable for Filters that will be used for actions such as email alerts, is this correct?
The document suggests that at 100 rules the issue becomes memory; does this mean you can resolve the issue and have more than 100 rules just by adding more memory to the system or is it more of a fundamental application performance limitation?

mark_wiggans

1. That is correct.

2. 100 is a general suggestion. Try increasing the number in small increments. Observe how the memory usage is affected by looking at the process Syslogd_Service.exe.

netlogix

wait, did you just get Kiwi to move syslog out of the Orion Database and off the Orion server? I just started on that! I am amazed at how many logs per hour are coming in! I wish Orion had a counter like Kiwi's. Let me know if you find any thing you can pass along, I'll do the same. If thats not what your doing, never mind .

byrona

LOL We are not moving to Kiwi though I think that may not be a bad idea for some stuff. I am working on a customer project where we will potentially be providing Log Management as a service and Kiwi is one of the potential products for the job. In all honesty I have really been let down by the options out there as far as Log Management goes.

netlogix

I started to see the CPU time on the syslog service and how DB disk time is spent with syslog and I decided that it isn't worth slowing down orion to collect syslog. (After I already had Orion, I had a need to gather syslog and so I thought - hey Orion does that! so I started to point everything there and I think the load is taking away from Orion's real purpose, so now I am moving it to Kiwi and then I'll forward the logs I want in Orion)