(@acastonguayvmware.com) kudos icon +

Feature Requests

Datatype-aware field extraction

Sometimes log messages contain embedded data with a fixed standard format, like XML, JSON or CSV, either when logging about configuration/state information or when the messages aren't really logs. Attempting to parse out any of these formats with regular expressions is difficult (and in the case of XML, strongly discouraged), especially when the structure includes nesting, lists or esoteric quoting/escaping rules.

For... more »
(@acastonguayvmware.com) kudos icon +

Feature Requests

Drop specific incoming messages

An administrator may deem some messages undesirable, either specific logs produced by a source or a whole source. Such messages may result in CPU/disk resources being expended unnecessarily. Undesired log messages may result in Log Insight's data store being rotated more quickly than desired. In terms of licensing, one may wish to drop log messages from unlicensed sources, restricting sources from which log messages are... more »
(@erikkringlie) kudos icon +

General Log Insight Q&A

Help with Solaris 10 syslog

Has anyone had any luck with getting a Solaris 10 server to send syslog into LogInsight?


I've tried:


*.debug @IPADDRESS


and other variations in the /etc/syslog.conf


Then restarting or refreshing via:


svcadm refresh svc:/system/system-log:default


svcadm restart system/system-log


But nothing seems to work. Any thought/help would be great.

(@jacob.curranacxiom.com1) kudos icon +

Feature Requests

Deduplication of Data

I was wondering if you guys could make the data be zipped/dedupped during the night? If it already does dedup or something I guess its fine but it would seem that log insight takes a lot more space then our other logging system. We are trying to move everything to log insight but space constraints don't seem to be matching up.

(@acastonguayvmware.com) kudos icon +

Administration of Log Insight

Tiered online, searchable data storage

When Log Insight's local capacity to store messages is exhausted, messages are archived to a remote NFS location. It would be beneficial if this flow could be tiered such that data was available online as today but moved to a slower & higher-capacity tiered disks as it ages.

Consider the use-case of keeping the most recent 50GB of data on SSD, migrating it to ~5TB of slower spindles over time while keeping it searchable,... more »