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 »

Submitted by (@b.lievers)

Voting

7 votes

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 »

Submitted by (@pwalker)

Voting

4 votes

Content Packs

vRops Agent Configuration

I have looked at the vRops Agent setup instructions and they don't make sense to me... Rather than copy/pasting it all in here, I have attatched a file with the setup instruction. 1. In the beginning of the file, the first two lines after "Configuring the vRealize Log Insight Agent". Goes on about the liagent.ini need to be modified. 1A. This is not true as the centralized configuration is used, correct ? That part ...more »

Submitted by (@ryom.michaelgmail.com1)

Voting

1 vote

Content Packs

Windows Firewall Advanced Content Pack

Extract more Details from Windows Firewall File-Log

(ContentPack is attached)

 

- Blocked Connections by Source IP

- Blocked Connections by Destination IP

- Blocked Connections by Source Port

- Blocked Connections by Destination Port

- Blocked Connections by Protokoll

- Blocked Connections by Hostname

- Disabled / Enabled Firewall

Submitted by (@markus.krausgmail.com)

Voting

8 votes