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.
Related
Currently, I have a Sentry.io account and push errors to the dashboard interface.
I was wondering if the following is possible:
Take the pages on the existing Sentry.io dashboard
Embed some of the panels and pages in a page on a custom website
Errors and interface would appear the same way on the custom website
Can interact with the interface and errors in the same way in terms of viewing sub-tabs and sub-pages
I'm primarily interested in the:
Projects tab and navigate to subtabs like Project Details and individual errors
Issues tab and the ability to search and view errors
Thank you.
Just came across Sentry a few weeks ago. According to the API documentation, it states the ability to GET, PUT/POST, and DELETE data even from Projects. So I think your API will allow you to push alerts to your site and if the site is interactive, you should be able to make changes( e.g. resolve issues) and it will also reflect on Sentry.
Keep in mind that the data coming from the API is unstructured, you might need to streamline what you want to show on your site depending on how your site is designed.
I am not sure if I am able to help in some way. I am also open to learning if you are able to discover how to do it or if I am wrong.
I need to make single page social media dashboard using kibana and elasticsearch for some big event in 2019, so that the dashboard show hom many likes it has on facebook or instagram, how many people are going etc (and some other informations ). I dont have much experience with kibana and elasticsearch so any advice would be helpfull. Any idea how can I do that ?. Also I need to have heatmap in the dashboard. Thank you in advance
That is a pretty broad question. Do you already have the relevant data in Elasticsearch? Because that would be the starting point.
For the visualization you could use a dashboard or the more customizable Canvas, which is pretty much like a data driven Powerpoint:
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.
i'm searching for working search ui demo or tutorial for building search UI/Frontend. At best for php or js.
I never builded a elasticsearch application, but I already made projects with lucene, solr, epoq and google search.
Already searched on inet but most example are very simple and incomplete.
Examples:
github.com/scotchfield/elasticsearch-react-example/
github.com/spalger/elasticsearch-angular-example
There also API for PHP and JS
www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/quick-start.html
www.elastic.co/guide/en/elasticsearch/client/php-api/2.0/_quickstart.html
What a example should contain (from my view)
* Basic Search Field
* Filter based on es fields index
* Resultview
* Filter interaction with results
* Paging
I was thinking something like this is already exits, but found no matching one. I think better ask, before invest time in creating.
Thanks in Advance
densanki
I found this live demo interesting:
http://demo.searchkit.co/imdb
If you already know ElasticSearch query syntax and some basic concepts like aggregations you may test all that on https://demo.elastic.co/app/kibana. But again, this would require some basic knowledge of Elastic stack.
Otherwise if you want just touch/try most common Elasticsearch features without going into implementations details then you may check these 3 demos for 3rd party SearchKit UI component.
There's also Elastic UI that you might be interested in: https://elastic.github.io/eui/#/
If you want something ready-made for the time-series use-case, you might want to check Sematext Cloud. There's a simpler UI than Kibana there, but there's API access, too, so you can develop your own.
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.