Minimize the amount data coming back from the indexersĪnother items that is also mentioned in many articles is the goal to filter your data early in order to help lower the number of events returned. In general, I exclusively make use of the stats command to avoid the use of the following commands: dedup, table, join, append.Ģ. The technique used above can also be used to address the use of the ‘append’ command as well. | stats count(eval(sourcetype=”splunkd”)) as metric_count count(eval(sourcetype=”audittrail”)) as audit_count by host (index=_internal sourcetype=splunkd component=Metrics) OR [search index=_audit sourcetype=audittrail Index=_internal sourcetype=splunkd component=Metrics What’s the solution? The above problems can be mitigated by combining your subsearch with your primary search and accomplishing the ‘join’ with the use of a stats command. This can go unnoticed, pay attention to the error messages that are returned with the use of these commands. This leads to a truncation of results, which leads to incorrect answers. By default, they have a timeout of 60s and a limitation of 50000 events (see subsearch_maxtime and subsearch_maxout in nf). With every use of these commands, the number of times that you need to access the indexers increases (and increases all of the communication and overhead that may be involved).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |