Repository navigation
docs(api): require a time range of at most 31 days on the alert event list - #1041
Merged
Merged
Conversation
… list start_time and end_time are now required on /alert-event/list. start_time must be less than end_time and the span must not exceed 31 days.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
POST /alert-event/listnow requiresstart_timeandend_time(Unix seconds).start_timemust be less thanend_timeand the span must not exceed 31 days; otherwise the API returns HTTP 400InvalidParameter.Updates the request schema (required fields, descriptions) and the usage notes in the zh and en specs (
on-call.openapi.*.json,openapi.*.json). The wording follows the existing/alert/listentry.