Skip to content
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

Closed
berggren opened this issue Aug 18, 2014 · 8 comments
Closed

Making time filters easier to use #1

berggren opened this issue Aug 18, 2014 · 8 comments
Assignees

Comments

@berggren
Copy link
Contributor

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)

@berggren berggren self-assigned this Aug 18, 2014
@krmaxwell
Copy link

Perhaps something like parsedatetime would help with this.

@berggren
Copy link
Contributor Author

berggren commented Jan 8, 2015

Interesting, I'll take a look at that. Thanks!

@mmaisel
Copy link

mmaisel commented Mar 28, 2015

How about similar relative time selectors like Splunk or Kibana?

@berggren
Copy link
Contributor Author

berggren commented Apr 6, 2015

@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!

@berggren berggren modified the milestone: 2015.12 Apr 14, 2015
@berggren
Copy link
Contributor Author

berggren commented Jun 4, 2015

I think moment.js can be of help here.
http://momentjs.com/docs/#/parsing/string-formats/

@pettai
Copy link
Contributor

pettai commented Sep 4, 2015

Maybe this is more nice than useful, but how about a slider for increasing/decreasing the time window
(example on how the slider could look, http://flog.sunet.se/event/websso/authentication-flow/)

@berggren
Copy link
Contributor Author

berggren commented Sep 7, 2015

@pettai Yes, we actually had that in the beginning :) I will revisit this idea when I start working on a new filter view.

@berggren berggren modified the milestones: 2016.6, 2015.12 Sep 24, 2015
@hiddenillusion
Copy link

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 timestamp.

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.

@berggren berggren modified the milestones: 2016.12, 2016.6 Jun 21, 2016
@berggren berggren modified the milestone: 2016.10 Oct 5, 2016
@berggren berggren closed this as completed Jun 6, 2017
jkppr added a commit to jkppr/timesketch that referenced this issue Dec 1, 2022
+ Configuration schema & file
+ API endpoint resource and routes
+ Some minor adjustments to make them work
berggren pushed a commit that referenced this issue Dec 5, 2022
* 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
jkppr pushed a commit to jkppr/timesketch that referenced this issue Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants