I was trying to find an opensource plugin to use LDAP/AD authentication for Elasticsearch/Kibana. I found Open Distro which is currently based on Elasticsearch 7.10.2, and I wanted to use the security plugin in my existing regular ES stack which works with 7.11.2, but it complains that it can't work with newer versions of ES. The problem is that I cant downgrade anyway without losing my data.
Is there another way (opensource) to integrate LDAP whether using Open Disto or another plugin?
You need to "downgrade" in that case if you want to stick with the latest version of this plugin I think.
You could start a new cluster with 7.10.2 and use reindex from remote to reindex your data in the "new" cluster. So read from 7.11 and write to 7.10.
Related
We are looking for an option in Artifactory Pro edition, where want to make a central dashboard for downloaded artifacts. Currently the each artifacts has count for # of downloads but we want to extend it more -
Number of downloads
Who downloaded it
from where its downloaded
Dashboard with filter criteria. Please help if anybody has build this type capability. I know probably we can use a plugin for this getting metrics and storing it to somewhere else. But we are looking for option provided by JFrog Artifactory.
Package view is part of the Platform versions (Artifactory 7.x and above): https://www.jfrog.com/confluence/display/JFROG/Package+Management
I suggest you upgrade as this is pretty much what you need.
On your current version there isn't such dashboard, but you can gather the information easily using the Artifactory Query Language: https://www.jfrog.com/confluence/display/JFROG/Artifactory+Query+Languagea
There is no metrics dashboard provided by Jfrog out of the box that would fit this need.
As mentioned by Angello you need to scrape the metrics yourself using the AQL or using different APIs provided by Jfrog then use that data to post onto a dashboard custom made for your usecase.
I've used Nutch and Elasticsearch many times before, however, I believe I was using the default setup to where Nutch used the binary transport method for communicating with Elasticsearch. It was simple and worked out of the box so I've used it alot.
I've been in the process of updating crawl system and it seems now the better option is to use the Jest REST api library.
However, I'm a bit confused about it...
First how do I install the Jest library to be used with Nutch and Elasticsearch. I know I can download or clone via Github but.. how is it connected?
Do I literally just update the dependencies in the /indexer-elastic-rest *.xml files for Nutch and then just build again with ant?
My first install of Nutch was using the binary zip. I just recently started using the src package so ant/maven is somewhat new to me - which is why this all a bit confusing. All the blogs and articles say to "and then rebuild with ant"...
Second - does the Jest library take care of all Java REST api code or do I have to write Java code now?
I am upgrading an install of SonarQube from 4.5.1 to 5.2. I wasn't part of the original install and when looking at the sonar.properties file to see what needs to be update in the new one, I see properties for "sonar.search".
What is Sonar Search? Why would I need to uncomment/update these properties?
I haven't been able to find any good documentation on the SonarQube website on what it is and "sonar" and "search" internet searches bring up way too many unrelated results to sift through.
It is an Elasticsearch instance used for indexing some database tables. It allows for example powerful search requests on issues. See the sidebar of page "Issues". It supports multi-criteria searches and displays valuable facets.
Default settings in sonar.properties are good enough for most of environments. JVM settings of this dedicated process could be overridden if dozens of millions of issues are stored in database.
As we have maintained explicitly an Elasticsearch service on our server, can we use that Elasticsearch service instead of inbuilt one which is in Sonarqube 4.5?
If not, then can we access built in Elasticsearch service on HTTP? If so, could you please tell us how to access it?
Thanks,
Pravin
SonarQube embeds an E/S server for its own needs, and this should remain a black box for SonarQube users.
In SonarQube 5.0, you will be able to enable ElasticSearch HTTP connector for debugging purposes - see SONAR-5692. But keep in mind that in no case, you should try to trick or modify the E/S servers launched by SonarQube.
I am completely new to web development and I want to set up a database search client on a website I am making because I do not want to write my own inefficient MySQL query strings. My plan is to use Elastic Search for this and my main question is:
Once my site is on a dedicated server somewhere, how do I install Elastic Search to the server, and/or what should I look for in a server so that I will be able to use Elastic Search?
You'll need a JRE, that's about it as far just getting started.
See http://www.elasticsearch.org/guide/reference/setup/installation.html for more details.
You'll probably want to run it as a service, If your using Windows you can download installers here. https://github.com/rgl/elasticsearch-setup/downloads
Hit me up if you need any help.