Across
- 2. Most efficient way to filter events in Splunk
- 7. Alert threshold configured for a specific value
- 8. An automated notification when a system enters an undesired state
- 9. A written record of an incident, its impact, the actions taken to mitigate or resolve it, the root cause(s), and the follow-up actions to prevent the incident from recurring
- 10. Splunk command used to combine and aggregate data
- 13. A combination of runbooks and steps to address broader events occurring in a system.
- 14. Container for where Splunk puts data as it is ingested.
- 15. Golden Signal that is the percentage of responses from a service that are failures
- 18. Alert threshold configured by comparing the current value to the average over a previous period.
Down
- 1. Golden Signal that is your actual load versus your expected capacity
- 3. The name, IP Address, or fully qualified domain name of the machine from which a Splunk event originated
- 4. Chart or graph-based representation of metric data
- 5. A collection of reports in Splunk compiled into a single pane of glass allowing you quick visual access to your data.
- 6. Golden Signal that is the amount of requests coming into a system
- 7. The file or directory path, network port, or script from which a Splunk event originated
- 11. Splunk’s Query Language
- 12. Golden Signal that is the time it takes to request and receive a response from a given system
- 16. Steps to quickly and accurately resolve a given issue or perform a common task.
- 17. Primary Splunk command used to perform calculations and transformations on data
