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
Making time filters easier to use #1
Comments
Perhaps something like parsedatetime would help with this. |
Interesting, I'll take a look at that. Thanks! |
How about similar relative time selectors like Splunk or Kibana? |
@mmaisel Yeah, I have been thinking of that too. I'll make sure to take a look at it when I'm strt working on this issue. Thanks! |
I think moment.js can be of help here. |
Maybe this is more nice than useful, but how about a slider for increasing/decreasing the time window |
@pettai Yes, we actually had that in the beginning :) I will revisit this idea when I start working on a new filter view. |
It'd also be convenient to be able to enter just a start date/time and not have to enter an end date/time. By default, it could just go from the start date/time to X amount of events (e.g. 500) or until the last Just sometimes a pain if I want to jump to a period of time but don't necessarily care when everything ends (or if I need to load the next page/500 events) to continue scrolling through the timeline. |
+ Configuration schema & file + API endpoint resource and routes + Some minor adjustments to make them work
* ContextLinks part #1: + Configuration schema & file + API endpoint resource and routes + Some minor adjustments to make them work * Bug fixes * Added missing fields to the VT example. * Making the black-formatter happy. * More fixes for the black-formatter. * Another linter fix. * Refactored the API endpoint. It now includes the changes suggested by the reviewer. + Better readable input verification + More granular error message on bad entries + Less log entries * linter * black-formatter * Adding a unittest for the API endpoint. * black-formatter * Refactored the API endpoint based on review comments. + Removed the validation from the API endpoint. + Moved validation to tsctl + Changed validation to use jsonschema + Updated tests * black-formatter * bug fix * Adding jsonschema to requirements.txt
Pulling New Updates
Add some fanciness to the parsing of the input boxes so that multiple input format will work (just a date, date in american format etc)
The text was updated successfully, but these errors were encountered: