Let's say I'm having few Kibana dashboards created upfront, and what I need to know is that will it be possible for me to add a UI component, for example a print button within the dashboard itself, in order for the user to print the dashboard externally? Apart from the feature to export it as a PDF, which is given by Kibana implicitly.
Any help could be appreciated. :)
Related
I'm really after some advice here please.
I have a membership website, and I am using WordPress to manage access to my paid subscriptions.
I'm interested in Kibana in terms of its' data visualization but my question is really one of whether I'm using it for the wrong purposes?
My point is: can Kibana be embedded and made to look white-labelled?
I'm pretty sure Kibana is really meant for internal use hence my question.
Thanks!
Yes that is possible. You can create various visualizations and have them integrated into one dashboard in Kibana.
This dashboard feature has capability to share these visualizations as discussed in this LINK. As an example, the share URL comes in the below format:
<iframe src="http://abc.myserver.com:5601/app/kibana#/dashboard/a6c99100-b2b2-11e7-8aa0-9fc1ad35f7e7?embed=true&_g=()" height="600" width="800"></iframe>
You can either share the current state of the dashboard with your users, or share them the most recent view of the dashboard whenever they reload their page.
Let me know if it helps.
I have a dashboard made out of different template-, chart, text-input and text-output nodes. Is it possible to update, clear or re-deploy the whole dashboard with its many tabs at once with a button in the UI?
many thanks in advance.
It doesn't make sense to redeploy the Dashboard UI.
If you make a change to the flow that creates the dashboard, then the dashboard will automatically update when you deploy the flow.
We connected superset with PostgreSQL and able to make charts and Dashboards. It's easy and really helpful to make dashboards. But now we are looking for the share functionality for dashboards which they also mentioned on their superset introduction pages(on Github and as well as on Airbnb site) that we can create and share the dashboard with others. So how to share dashboard with other users?
Sharing a chart should be easy. You can use the button as shown on the picture:
It is situated on the same page as where you create/edit your chart.
Also to share the chart you'll need to configure a public user and grant him all privileges required to open the chart.
This might sound a bit confusing but here it goes.
I have a 'Default' dashboard which shows a combination of visualization and dashboards. Basically i am showing a lot of customers on a default dashboard.
The entries on this dashboard will remain same and the search will narrow down once the user clicks a particular customer on visualization {say bar-chart}.
Now I want that when user clicks on the bar chart or does a search like cust_name , it should show a another dashboard instead of the default one which i configured for "customer specific detail"
I am not sure how to do this
There is no such feature in Kibana 4.x.
You can define the dashboards you desire to be opened and add the filtering visualization from the main one.
Also you can write a simple web page to call embedded kibana dashboards with queries injected when calling the dashboards.
We use Kibana, ElasticSearch and Logstash to monitor the health of production systems.
When fatal errors are logged, then handled by our support staff, we would like to be able to tag them as "Handled/Fixed" as well as insert a comment, within our Kibana dashboard.
This way we could set up a dashboard that displays only "Unhandled" errors that haven't been looked at by the support staff. A very basic ticket system, if you will, based on production logs.
Is there any plugin for Kibana that provides this feature?
If not, could a gentle soul provide a high-level overview of the development that would be required to write such a plugin?
I would think you could do this with a Javascript file that gets included in the Kibana dashboard.
You would write a file (let's pretend it's called support.js) and then add the to the Kibana HTML.
Then you can inspect the DOM that Kibana generates and:
Add a button where needed.
Show a modal popup when the button is clicked.
Wire up the save button to make AJAX calls to ES. (Marking a ticket as handled/fixed).
The script would introduce new fields to the documents and then it's easy to configure Kibana to filter on the fields.
That's the most orthogonal way to try and add functionality without getting into the actual Kibana code.