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.
Related
I want to create a new space in kibana and create a new user , attach a role with specific access and only to the space. This is a straight-forward thing with lot of docs provided by elasticsearch itself, but however there is one thing that I cannot find any clear documentation on. Does kibana support RBAC without enabling security features in elasticsearch? Is it possible to create roles in kibana without enabling security features in elasticsearch? I'm almost sure that it is not possible but since there is not direct wordings in the documents stating the above, I'm skeptical about it and hence posting here for expert suggestions.
I'm using kibana version 7.7.1. In my dashboard I'm not able to see the word "security" anywhere as described in the document. Posting a sample screenshot below.
Finally Found an official document that states the same. To answer the question, Yes Kibana doesn't support RBAC in a standalone manner. It depends on elasticsearch.
https://www.elastic.co/guide/en/kibana/7.x/using-kibana-with-security.html
Heyy, I'm looking for up-to-date kibana plug-in resources to help me learn and understand how to develop one.
All the resources I've found are out-of-date.
Can anyone help, please?
I suggest understanding plugin directory structure for traffic plugin which would be one of simplest plugin to understand and you could directly add it to your installed plugin folder in kibana and see it working.
Other than that I would also suggest you do read Tim Roes blogs for developing kibana plugins.
Last I would also suggest to use elasticsearch discussion forum for kibana related issues as well for quicker responses.
As kibana has different js files which loaded synchrnized way. you can use as it required.
I am trying two options.
One is not to store source code
If it is not possible how to delete project from sonar database?
I tried with "sonar.import Sources=false" but this is not working for sonar version 6.1(deprecated after 4.5 version).
If I delete the project,will source code remain in database?
Storage of source code in database can't be disabled because it's used to display data in webapp.
Source code is indeed dropped from db when deleting a project.
This is late, but might be helpful for someone:
Sonar usually cache the project for performance purpose via squid mechanism, then thru queue mechanism it stores the project data in internal h2 database which can be changed to few supported databases, then you will be having advanced options to manipulate data on database(things like fail-over cases can be achieved), not that I know of any way of not to store project data in database.
Unless you configure certain user, default user can be admin to sonar dashboard with password as admin, Login to console and navigate to Administration-> projects->Management, now delete n number of unnecessary projects. Once you do this Sonar dashboard will not be able to show the project again until you re-analyze same project. To make sure this worked,after re-analyzing project click on the project on dashboard and check the version under Activity.
Additional info: If you modify the maven project code, first build the project & then do sonar:sonar for latest modifications to be reflected.
I agree with other answer, elaborating in few lines..
The property sonar.scm.enabled was enabled by default and during the analysis a lot of issues were assigned to the same author, though this was not the real author of those issues.
This is because that git user was the responsible to migrate the code from a previous version control.
I want to know if is there any way to unassign all issues assigned to a specific author, using some kind of bulk change or a specific configuration during an analysis.
Sonar version: 5.1.2
You haven't mentioned your version of the SonarQube platform, so I'll assume 5.1.*.
In the Issues page, do an Assignee search, and then use Bulk Change to re/un-assign the results.
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.