WHAT WE'RE WORKING ON - LOG & EVENT MANAGER EDITION (UPDATED October 18, 2016)

Capt._Obvious over 8 years ago Less than one minute read time

To check out the most up-to-date information regarding What We're Working on, please visit the LEM Product Roadmap page.

Be sure to let us know in the Log & Event Manager Feature Requests forum, if there are features you're really keen on. This list doesn't enumerate a lot of the features we're looking into for long term development and further releases, but we continually use Thwack as our biggest source of feedback.

Top Comments

Parents

hitnrunxx over 8 years ago

Letting you know here, as asked. List of my feature requests/issues:

1) Allow visibility of logs to be broken up by groups. Some people need to be able to see every log, but some people should only be able to see the logs pertaining to their systems.
2) 2 TB is simply not big enough. We need more historical data space. Doing fancy "back it up to another system, and restore it when you need to look at it, just so you can be compliant" is not feasible.
3) We need time-based data retention. We need to be able to mark some data for longer retention, especially for compliance. I don't need firewall logs for more than a month. I do need PCI machine data for a year. The large volume of firewall logs will push off the PCI logs before I am ready. Again, the whole "back up your logs elsewhere" isn't very feasible.It also makes it difficult to see trends over a long period.
4) I need to be able to do longer ndepth searches, without having to rely on Crystal Reports.
5) Crystal Reports? Seriously?
6) Ability to group syslog nodes with the same ease as windows nodes. Yes, I know you can manually enter them all in a group, but if the system already detects them, I should be able to just highlight them and add them. This goes for offline nodes too.
7) Did I mention scrapping Crystal Reports? Having to do a giant report (say, for all logons) before I get to parse the data down (say, for a specific user) is incredibly cumbersome.
- Cancel
- Vote Up +4 Vote Down
- More
- Cancel

Comment

hitnrunxx over 8 years ago

Letting you know here, as asked. List of my feature requests/issues:

1) Allow visibility of logs to be broken up by groups. Some people need to be able to see every log, but some people should only be able to see the logs pertaining to their systems.
2) 2 TB is simply not big enough. We need more historical data space. Doing fancy "back it up to another system, and restore it when you need to look at it, just so you can be compliant" is not feasible.
3) We need time-based data retention. We need to be able to mark some data for longer retention, especially for compliance. I don't need firewall logs for more than a month. I do need PCI machine data for a year. The large volume of firewall logs will push off the PCI logs before I am ready. Again, the whole "back up your logs elsewhere" isn't very feasible.It also makes it difficult to see trends over a long period.
4) I need to be able to do longer ndepth searches, without having to rely on Crystal Reports.
5) Crystal Reports? Seriously?
6) Ability to group syslog nodes with the same ease as windows nodes. Yes, I know you can manually enter them all in a group, but if the system already detects them, I should be able to just highlight them and add them. This goes for offline nodes too.
7) Did I mention scrapping Crystal Reports? Having to do a giant report (say, for all logons) before I get to parse the data down (say, for a specific user) is incredibly cumbersome.
- Cancel
- Vote Up +4 Vote Down
- More
- Cancel

Children

No Data

Thwack - Symbolize TM, R, and C