I have alerts configured expires after 100days and scheduled to execute search query every 10mins. I can see alert search job is available under "| rest /services/search/jobs" and utilizing disk usage.
I could not find anything about this in the logs. Could someone help me to understand relationship between disk quota utilization vs triggered alert retention period?
Please understand that alerts *never* expire. They will continue to run until you disable or delete them.
What *does* expire are the alert *results*. That is the data found by the query that ran to trigger (or not) the alert. That data is kept in the search head and is subject to disk space limits based on the role of the user running the alert. Without such limits, the SH risks running out of space to use to store more search results.
IMO, there's very little need to preserve alert results beyond the standard 2p. Perhaps 24 or 72 hours, but not 100 days.
Please understand that alerts *never* expire. They will continue to run until you disable or delete them.
What *does* expire are the alert *results*. That is the data found by the query that ran to trigger (or not) the alert. That data is kept in the search head and is subject to disk space limits based on the role of the user running the alert. Without such limits, the SH risks running out of space to use to store more search results.
IMO, there's very little need to preserve alert results beyond the standard 2p. Perhaps 24 or 72 hours, but not 100 days.