I am building a proof of concept using Elasticsearch Logstash and Kibana for one of my projects. I have the dashboard with the graphs working without any issue. One of the requirements for my project is the ability to download the file(csv/excel).
In kibana the only option i saw for downloading the file is by clicking on edit button on the visualization created. Is it possible to add a link on the dashboard that would allow users to download the file without going into the edit mode. And secondly I would like to disable/hide the edit mode for anyone other than me who views the dashboard.
Thanks
To export data to csv/excel from Kibana follow the following steps:-
Click on Visualize Tab & select a visualization (if created). If not created create a visualziation.
Click on caret symbol (^) which is present at the bottom of the visualization.
Then you will get an option of Export:Raw Formatted as the bottom of the page.
Please find below attached image showing Export option after clicking on caret symbol.
FYI : How to download data in CSV from Kibana:
In Kibana-->
1. Go to 'Discover' in left side
Select Index Field (based on your dashboard data)
(*** In case if you are not sure which index to select-->go to management tab-->Saved Objects-->Dashboard-->select dashboard name-->scroll down to JSON-->you will see the Index name )
left side you see all the variables available in the data-->click over the variable name that you want to have in csv-->click add-->this variable will be added on the right side of the columns avaliable
Top right section of the kibana-->there is the time filter-->click
-->select the duration for which you want the csv
Top upper right -->Reporting-->save this time/variable selection with a new report-->click generate CSV
Go to 'Management' in left side--> 'Reporting'-->download your csv
In Kibana 6.5, you can generate CSV under the Share Tab -> CSV Reports.
The request will be queued. Once the CSV is generated, it will be available for download under Management -> Reporting
I totally missed the export button at the bottom of each visualization.
As for read only access...Shield from Elasticsearch might be worth exploring.
Related
My REST service is performing lots of http queries which I would like to monitor in my dashboard. In it's APM view I can choose from servlet.request operation name or netty.client.request. The former one is the primary operation, while the latter one is additional operation.
What I managed to do was that I am able to build a widget in the dashboard which uses metric-type source like this: default_zero(sum:trace.netty.client.request.hits.by_http_status{$env,$service,!http.status_code:200}.as_count()) and it works, it shows me the number of errors client is getting, but when I click on the widget and choose show related traces I do not see traces related with netty.client.request operation, but the ones related with servlet.request. The reason for it was that it generates following query env:prod service:payments-braintree-gateway -#http.status_code:200, which does not include operation name, nor "all spans" (next paragraph explains it)
So I went to traces view in APM and I tried doing the query I wanted, there. Initially I was only able to choose one operation in the filters - servlet.request, but I noticed a button next to search bar labeled in, where you can choose in which set of spans to search for. There are 2 options: service entry spans and all... Switching to all made it possible to create a query I am interested in: $env $service operation_name:netty.client.request -#http.status_code:(200) and it works... So the only thing left was to use it in the dashboard.
Now when I am back in the dashboard's widget I fiddled with the query in json, I tried to edit context menu links, I even changed metric type from "metric" to APM... All in vein. Looks like it is impossible to use non service entry spans in widgets.
Funny thing is that I even exported from APM's service view error graph to dashboard and then clicked "show related traces" it still showed incorrect thing, while "show related traces" option in the graph in the APM takes me to the correct view in traces
So... is it possible to fix "show related traces" button in the DataDog dashboards?
Looks like the only doable solution is to hide standard traces link and create new custom link. Downside is that it is going to open a new APM browser tab instead showing traces in the modal at the right hand side of the screen, but at least it works. Still ideas how to tackle it differently are welcome of course :)
is there a way to open spotfire web player in first page always.
My web player link is opening analysis in different pages not on the home page.
Much appreciated
thanks
Create one Document Property "OnOpenAnalysis" with DateTime:-
Write ironpyton script to that document property
ScriptName
Write below line in Script
Document.ActivePageReference = Document.Pages[0]
Add DataFunction using Open R,
use below code
input <- systime()
assign output as document property and select document property "OnOpenAnalysis"
you are done.
Make sure that when you save your analysis, you save it showing the first page.
Then modify so that state isn't kept per user. Go to Edit -> Document Properties -> Library tab, and uncheck "Remember personalized view for each Web Player user":
I am using Oracle OBIEE 11.1.1.5.0
I have 2 existing views saved as separate reports. One is a Pivot; the other is a Table. Their data sources are unrelated.
I want to be able to combine both views into one compound view within one report, so I can export both to the same Excel file.
Please let me know how to implement. Please excuse my word selection; I am very new to this product.
Edit: It was suggested that I include both reports on a dashboard, and then export from there. Here are my available dashboard options. Am I missing an Export option that should be visible for the version I am using? Am I not seeing it because I don't have full permissions?
long story short, it seems as though OBIEE 11.1.1.5.0 does not give you a seamless way to export entire Dashboard pages to Excel.
HOWEVER, there is an ugly way to do it.
Page Options --> Print --> Printable HTML --> Save As --> .xls
see this thread for more info.
here is another thread.
Is my expectation valid? If yes, please guide me.
Local machine->local server process-> I generate Birt report-> which contain hyperlinks hard coded for example: http://www.ip_one.com/birtserver/parameters...(this is fine and points to another report and get me the report also when I hit the Url from inside the generated pdf report).
Now, what I need is to change ip_one to suppose ip_two once I hit the hyperlink which is inside the pdf(on the fly) keeping all the other parts of the url intact.
I am using birt-rcp-report-designer-4_2_2.
Thanks in advance.
It sounds like you are trying to dynamically create a hyperlink at report run time.
In the properties editor of the report item that has your link (i.e. label), edit the hyperlink. In the Hypelink Options (pop-up) to the left of "Location" field is the button ab| select 'JavaScript' Syntax.
You will be able to create the URL using JavaScript.
For some reason when somebody performs a search on my site the search results do not display underneath the search box, they appear on the far left of the screen.
Any ideas of what file this would be configured in?
Let me correct myself it's not the search results but the search suggestions
I can't offer a direct solution to your problem, but turning on template hints might point you in the right direction. In the Admin, go to System > Configuration, Select your store view from the scope drop down at the top left. Unless you're running multi-store, or have changed the name of the default store it'll be called "Default Store View". Then scroll down to "Developer" and open up the "Debug" section. Turn on both Template Path Hints" and "Add Block Names to Hints". This will add a div with a red border around each template in your layout and a heading which includes the name of the template. It will liklely completely screw up your page layout, but will show you which template generated every tag on the page and help you track down the issue.
The DeveloperToolbar extension makes turning this on/off quickly much easier, but I wouldn't recommend deploying it to a production site.
Alan Storm's indispensable CommerceBug is another tool which is very handly for tracking down front end issues. CommerdeBug can show you the layout handles and the aggregate layout XML used to generate the current page. Both of which are useful for determing why a specific block was (or wasn't) included.
So in case anybody else runs into this or wants to move where their search suggestions display it is in styles.css under .searchautocomplete.