You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not every company wants the same data in its Splunk system, so different TIE columns may not be needed in the system. However, each column field costs Splunk index volume, download and processing time.
What
Every available column field should be selectable via the web interface and only the activated column fields should be used. The default should be selected and the rest should be available via advanced setting button.
The following JSON elements are available in the TIE and should be usable:
Why
Not every company wants the same data in its Splunk system, so different TIE columns may not be needed in the system. However, each column field costs Splunk index volume, download and processing time.
What
Every available column field should be selectable via the web interface and only the activated column fields should be used. The default should be selected and the rest should be available via advanced setting button.
The following JSON elements are available in the TIE and should be usable:
Default activated:
A great example can be:
How
The text was updated successfully, but these errors were encountered: