-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Kibana 4.5 - Templated dashboard support #9990
Comments
I'm not entirely sure, but this sounds like it would be addressed by #4489 Can you explain your specific use case in that ticket? If you don't think it would be addressed by that, we can reopen this. In any either case though, a detailed description of your use case would be helpful. |
Hi Court,
Could you provide link to documentation how it's done? As noted in the list of references in my original listing, the only way is to heck the source code.
On Jan 30, 2017, at 7:51 AM, Court Ewing <[email protected]> wrote:
I'm not entirely sure, but this sounds like it would be addressed by #4489
Can you explain your specific use case in that ticket? If you don't think it would be addressed by that, we can reopen this. In any either case though, a detailed description of your use case would be helpful.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@aslng I don't fully understand your use case, so I'm not sure what documentation to point you to, if any. |
My use case is very simple.
In Kibana Discovery, I have the following logs for doctype "doctype1". _id part_type field2 field3
57d48e05-949f-5b34-a750-0b8e5e9b74ac 123 ... ...
9c81ab6b-52b2-5fb9-b7f9-f785ca40c8a0 53 ... ...
For the part_type field, I would like to make it as a URL link. When kicking it, it will search and show all records in another doctype "doctype2" where its part_type has the value equal to the field {{value}} (i.e. 132 or 753 depending on which link is clicked). I know how to format the field as URL if the value "123" is the _id in "doctype2".
However, if part_type is just a data field in "doctype2". How could this be done?
In doctype "doctype2", there will be documents like the following: _id part_type ... ...
df5a6f4a-3ac5-5be2-9204-b3dc7a0e4260 7 ... ... 5d6421eb-bf81-53e4-81b0-f2a1ff1982f9 123 ... ... c2e254e6-ef07-5b07-9db0-f5d520757eab 123 .... ... c459a223-ec50-5c69-9e5b-0e024adfa75a 53 ... ...
Basically, when the URL corresponding to "123" in doctype1 (in Discovery) is kicked, it will search and show the 2nd and 3rd records in doctype2 (in Discovery, Visualize or Dashboard). When the URL corresponding to "53" in doctype1 is kicked, it will search and show the 4th record in "doctype2".
Thanks,Anthony
From: Court Ewing <[email protected]>
To: elastic/kibana <[email protected]>
Cc: aslng <[email protected]>; Mention <[email protected]>
Sent: Monday, January 30, 2017 11:04 AM
Subject: Re: [elastic/kibana] Kibana 4.5 - Templated dashboard support (#9990)
@aslng I don't fully understand your use case, so I'm not sure what documentation to point you to, if any.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Thanks for the details. We don't have documentation for this, but I encourage you to set up the search and filters that you'd want to ultimately link to and look in the URL for the |
If there are million different part_types, does it mean that we have to set up million different search/filters to link? Or the part_type could be passed to the search/filter template? Even there is no doc, could you pls briefly highlight how to pass the part_type to the search/filter template to search? |
Any new support in Kibana that my help? |
I find a way to create URL with all _a and _g parameters need to invoke the target dashboard. It works with any source code patch. |
@aslng could you please provide the details how it is achieved. |
What we need is a way to create a link to a search.
Basically, what's required in #168 but it has to work in Kibana 4.
After reading the following related links, the support comes and goes in Kibana 2 and 3. There doesn't seem to have a good solution in Kibana 4.0 except the ugly hack provided by "childe" in #4269.
If there is a solution, any documentation on it for the URI templatization?
Other related discussions are:New value added to drive a business result
#947 ==> 2014 #168
https://www.elastic.co/blog/kibana-3-milestone-4
#2502
#4269
#4489
enhancement
The text was updated successfully, but these errors were encountered: