-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Added new data query option "allow_past" #10112
Added new data query option "allow_past" #10112
Conversation
Calculate "after" and allow it to extend to the past if "allow_past" is given
Hi @stelfrag , Please, can you also change the swagger file and yaml file with this PR for we do not have options without documentation? Thank you! |
good point !!! 👍 |
@stelfrag I tested now with I executed the following requests to simplify the comparison:
|
Ah, yes I have been tricked quite a few times by this. Please escape the & because you sent the command to the background 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After to add quotes for curl 👀 , everything worked as expected.
Thank you @stelfrag !
Summary
Adds a new query option
allow_past
for the data endpoint that will allow the after parameter to extend before the first timestamp stored. The entries that do not exist will be returned as nullComponent Name
database
Test Plan
/api/v1/data?chart=system.cpu
/api/v1/data?chart=system.cpu&options=allow_past