Scheduled Search V2 #185
Merged
Scheduled Search V2 #185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fjerlov-cs
force-pushed
the
fjerlov/scheduled-search-v2
branch
from
4482383 to
794c26a
Compare
fjerlov-cs
commented
Mar 24, 2025
fjerlov-cs
force-pushed
the
fjerlov/scheduled-search-v2
branch
from
794c26a to
016d28e
Compare
|
@fjerlov-cs @SaaldjorMike Do we need to make similar changes to |
SaaldjorMike
approved these changes
Mar 26, 2025
We do need to update that project as well, yes. |
SaaldjorMike
added a commit
that referenced
this pull request
Mar 26, 2025
This reverts commit c178856.
SaaldjorMike
added a commit
that referenced
this pull request
Mar 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New
./bin/humioctl scheduled-searches-v2command to use the new scheduled searches endpoints and types../bin/humioctl scheduled-searchesstill works as intended but will not support creating scheduled searches running oningesttimestamp.If trying to install an old scheduled search yaml file,
scheduled-searches-v2will try and install it using the deprecated mutation.Release notes for 1.180:
Scheduled searches can now also run on the @ingesttimestamp. A configurable Max wait time property on scheduled searches that runs on @ingesttimestamp is used to catch events that are delayed in the ingestion pipeline, or to wait for query warnings about missing data and errors. The @ingesttimestamp is the default timestamp set on all new scheduled searches.
With this change, the GraphQL mutations createScheduledSearch and updateScheduledSearch have been deprecated for removal in 1.231 and createScheduledSearchV2 and updateScheduledSearchV2 will replace them.
For more information about scheduled searches and their timestamps, see Ingest delay for scheduled searches. For information about the Max wait time property, see Max wait time.