-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for creating new signals without re-indexing all data #1676
Comments
Hi @DanAvni , Thanks for the suggestion. I have a few questions to help me understand. Q1. If signals do not index the log, what do they do? Is it a way to save a search expression? Q2. If what you want is saved searches, have you tried pinning the search in the HISTORY window? Thanks. |
Maybe I wasn't clear so let me explain: |
Thanks for the clarification. |
Hi @liammclennan, Any chance this will be added soon? My data has grown to over 6TB of logs and I am in the process of adding a new property to events that I will need to filter upon. When I will add a signal on the new property it will be a waste of CPU/Disk time indexing all the events as nothing contains it. |
Hi @DanAvni It is not planned at the moment. The team is currently busy building distributed queries for Seq clusters. |
I have 2TB+ of events and need to create a new signal. I do not care about filtering events earlier than now as I know they are not relevant and/or do not exist. When I create the new signal, all data is re-indexed, which is a huge waste of time as it takes days to complete. Please add support for adding a signal without re-indexing of old data.
The text was updated successfully, but these errors were encountered: