We have completed an upgrade procedure from 5.3.1 to 5.6.5 and then 6.1.1 (we have followed your procedure) Kibana previous versions: 5.3.1 Elasticsearch previous version: 5.3.1 and 5.6.5 Kibana new version: 6.1.1 Elasticsearch new version: 6.1.1 Server OS version:Ubuntu 16.04.2 LTS Browser version: Chrome-63.0.3239.132 (Build oficial) (64 bits) and Firefox-57.0.4 (64-bit) Browser OS version: Microsoft Windows Server 2016 Datacenter Original install method (e.g. Download page, yum, from source, etc.): from.tar.gz Description of the problem including expected versus actual behavior: We have problems Authentication Exceptions which avoiding to use Kibana. Those problems weren't with the 5.3.1 version. It have emerged after upgrading.
Note the three different types. Here alfresco produces the majority output as DEBUG log level is enabled. I added a query each for the types I defined in my Logstash config. This is just a very simple example on how to filter and search in the logs. What is next? There are numerous ways to configure Logstash for your needs. In the following posts I will explain.
How to use the log4j socket appender instead of files to transmit messages to Logstash. Is is normally not the best idea to run it on the Alfresco repository server. How to use a json log4j layout to auto parse log messages in Logstash. How to view Alfresco audit data in Kibana using Logstash and Elasticsearch. It is indeed very easy to set up and get started.
![Download Download](/uploads/1/2/5/4/125448699/728675987.png)
What I mean with “normally not the best idea to run it on the Alfresco repository server” was that when you have limited resources on the server and it also adds complexity to your production environment I would recommend to scale out if possible. And with Logstash it is really simple (I will show how in a coming post). The actual load it put on the server depends on the amount of logging and formatting done. But in any circumstances one of the great benefits of this approach is that you will aggregate all logs (repo, share, solr, db etc) into one with a user friendly UI and normally these logs resides on different servers anyway – so maybe performance is not the no #1 reason for separating log analysis from the Alfresco servers.
If you want to use a Kibana release in production, give it a test run, or just play around: Download the latest version on the Kibana Download Page.