Feature Requests

Let us know what will make Log Insight even better!  Add new ideas & vote on other feature ideas to let us know what's important to you.

Showing 7 ideas for tag "packs"
(@b.lievers) kudos icon +

Feature Requests

tag new data by source (hostname) instead of via VIP

Some Content packs needs an own VIP to tag incomming data so the dashboards of that content pack can filter it.
For instance the NetApp content packs relies on it. This would mean that when you use a broad spectrum of content packs, you need extra VIP's just to tag data special for those content packs.

What if you could tag syslog data based on the source. (IP address or hostname).... or by dataset....
This would bring... more »
(@pwalker) kudos icon +

Feature Requests

Application Autodiscovery

When Content packs are added post agent deployment on large estates, each agent's configuration requires updating to add the relevant section to the liagent.ini or the liagent-effective.ini. The recommended route is via the UI, but when the estate is large and there are many forwarders, then it becomes quite a task to determine which content packs are relevant to each of the target agents.

It would be fantastic (and... more »
(@pawel.orzechowskiindevops.com) kudos icon +

Feature Requests

Palo Alto content pack

There used to be Palo alto content pack https://blogs.vmware.com/management/2015/03/palo-alto-networks-content-pack-now-available.html but this is no longer available.

 

Does any one have old version that can be shared for use with fields, query and alarm definitions?

 

PS. This post should be in the Content Packs compain but I can not move it after it is created.