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

CSV export does not use current search time range #2795

Closed
edmundoa opened this issue Sep 7, 2016 · 0 comments
Closed

CSV export does not use current search time range #2795

edmundoa opened this issue Sep 7, 2016 · 0 comments
Assignees
Labels
Milestone

Comments

@edmundoa
Copy link
Member

@edmundoa edmundoa commented Sep 7, 2016

Expected Behavior

When doing a search, I expect the CSV export values to contain the same time range all other search elements use, even if I modify the search bar time range but didn't execute the search.

Current Behavior

Modifying the time range in the search bar without executing the search will use the new time range on the CSV export.

Possible Solution

Rely on the data coming from SearchStore.getOriginalSearchURLParams() instead of getting the updated configuration from the store.

Steps to Reproduce (for bugs)

  1. Do a search, for instance a relative search for the last 5 minutes
  2. Change the time range to another one, e.g. relative search in the last 1 day
  3. Export CSV results
  4. Results contain data from last day, and not only the last 5 minutes

Your Environment

  • Graylog Version: Graylog 2.1.0
@edmundoa edmundoa added bug web labels Sep 7, 2016
@edmundoa edmundoa self-assigned this Sep 7, 2016
@edmundoa edmundoa added this to the 2.1.1 milestone Sep 12, 2016
edmundoa added a commit that referenced this issue Sep 12, 2016
Generate CSV export link using the time range of the current search,
instead of the current value of the time range inputs.

Fixes #2795
@jalogisch jalogisch added S2 P3 labels Sep 12, 2016
bernd added a commit that referenced this issue Sep 12, 2016
Generate CSV export link using the time range of the current search,
instead of the current value of the time range inputs.

Fixes #2795
@bernd bernd closed this in 70f065a Sep 12, 2016
@kroepke kroepke added the triaged label Sep 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants