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

Histogram markers all contained in one or just a few markers #854

Closed
DannyJoris opened this issue Jan 21, 2014 · 4 comments
Closed

Histogram markers all contained in one or just a few markers #854

DannyJoris opened this issue Jan 21, 2014 · 4 comments

Comments

@DannyJoris
Copy link

I'm liking the histogram markers, but for some reason, using my query, they're all contained into one marker. I've had other queries where 3 markers were placed correctly, with a few results in them and then a 4th marker containing all the rest of the markers.

I'm using a query that should have results spread all over the histogram. For the histogram I'm using a ES date field and I use the same date field on the sort query for the markers too.

graph: https://www.dropbox.com/s/ex8x29lj3gegog5/Screenshot%202014-01-21%2012.11.00.png
settings: https://www.dropbox.com/s/rmrdfghowktwegn/Screenshot%202014-01-21%2012.15.23.png

rashidkpc pushed a commit to rashidkpc/kibana that referenced this issue Jan 21, 2014
@rashidkpc
Copy link
Contributor

I made event clustering less aggressive, I should probably add a switch to turn it off, however I should note that the markers can take a lot of resources to place if you have hundreds of them since they're individual elements.

wking added a commit to wking/kibana that referenced this issue Jan 23, 2014
We store our bes timestamps in UTC [1], because that doesn't depend on
the timezone of the log-generating host.  However, most folks don't
prefer to see their local time [2].  Upstream learned support for this
in 6696e13 (option to adjust table time field to browser's local
timezone, 2013-12-04 [3]), which landed a month and a half after
v3.0.0milestone4 (the last time we synced with upstream).  Sync again
to pull in this change.  By merging the current master, we pull in an
additional 104 non-merge commits:

  $ git log --oneline --no-merges 6696e13..origin/master | wc -l
  104

but there's no sense in stopping halfway.  That would just delay any
integration issues (of which I am aware of none) until later.

[1]: https://github.com/wking/bes/blob/v0.3/bes/__init__.py#L76
[2]: elastic#95
[3]: elastic#95 (comment)

* origin/master: (184 commits)
  Use -moz-box-sizing for firefox kibana-container
  Improve annotation tooltip on light theme
  Get rid of the reverse
  Re-fix overly broad cluster, events need to be sorted correctly
  Fixed overly broad event clustering. Re: elastic#854
  Resolve ids from list at initialization
  Added license information for vendor packages
  make panels 100% width on mobile
  Improve button positioning
  Improve droppable spaces when dragging
  Revert max span to 12
  Align row buttons with panels
  Improve visibility of available drag spaces
  Add subtle border to panels, improve dragging representation
  Fix column panel, closes elastic#832
  Fixed resize events
  Extended save/cancel to row and dashboard editors. Allow rows to overflow gracefully. Normalized spacing between panels
  Add the content of the panel to a panel-content container
  Add git commit to built versions
  cleanup comment
  ...
@bonobo78
Copy link

bonobo78 commented Feb 2, 2014

Having the same behaviour. But all markers sticks at the end of the
timeline (histogram's right edge).

Cdlt,
Frédéric Renan

2014-01-22 Rashid Khan [email protected]:

I made event cluster less aggressive, I should probably add a switch to
turn it off, however I should note that the markers can take a lot of
resources to place if you have hundreds of them since they're individual
elements.

Reply to this email directly or view it on GitHubhttps://github.com//issues/854#issuecomment-32975655
.

@rashidkpc
Copy link
Contributor

Thats usually due to the query you've specified and the sort order.

@rashidkpc
Copy link
Contributor

I'm going to close this, the new clustering algorithm solves it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
@DannyJoris @rashidkpc @bonobo78 and others