I'd like to see us add the Log Insight query strings on kb.vmware.com articles where applicable.
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
Everytime I want to import a content pack, I never see the "import content pack" button because it is at the bottom of the screen (and sometimes my web browser opens pretty big).
Move the button up!
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 »
Since Citrix still has "some marketshare", it would make sense to deliver a CP for it.
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 »
Some content packs can impact the entire LI clusters performance.
LI should be able to determine based on known best practices if a content pack will potentially be problematic and a warning icon/alert should notify administrators of this situation.
It would be fantastic (and... more »
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.
IIS CP xtracts wrong fields.
See attached Screenshot.
Prior vLI 3.6 I have not noticed this behavior