Skip to content

Conversation

@nstielau
Copy link

First off, let me express my comprehensive love of Kibana 3.

With that out of the way, let me describe the use-case: I wanted a general dashboard that showed multiple pinned queries (so they are nice and short with the alias), that could be used to get an at-a-glance view of things, while having the ability to drill down (or, in this case, filter out certain queries). For example, a single system might have haproxy, python and cassandra log events, and I'd want the dashboard to show all three, with the ability to remove hproxy and cassandra queries to view only the python events. Does this use-case make sense?

The CSS styling could be better, but I thought I'd get feedback before diving in further.

Thanks,

-Nick

@spalger
Copy link
Contributor

spalger commented Aug 29, 2013

Correct me if I'm wrong @rashidkpc but isn't the idea behind pinned queries to have a set of "soft locked" queries and a set of queries that can be changed at will?

Probably unrelated side note: If you pin all of your queries, then add an unpinned query, the only way to get rid of it is by pinning it and then deleting it once it's pinned.

@rashidkpc
Copy link
Contributor

Affirmative on both. The 2nd is a fairly easy fix. Make a new ticket for it.

@spalger spalger closed this Aug 30, 2013
w33ble added a commit that referenced this pull request Oct 6, 2014
Reset the aggParams on agg change
harper-carroll pushed a commit to harper-carroll/kibana that referenced this pull request Jul 11, 2016
Changes based on discussion with Lucas
edmarmoretti pushed a commit to edmarmoretti/kibana-pt-br that referenced this pull request Sep 7, 2025
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 this pull request may close these issues.

3 participants