Downloads

Use the link above to download the preferred version. The zip version contains built-in Java JRE, which is required to run the Logging Hub (in the zip version, the incoming data are logged only to a file). The Vagrant and Docker versions contain a virtual machine with all settings, so you can try full Logging Hub functionality (in these versions, the incoming data are logged to a file and Elastic and can be visualized in pre-installed Kibana).

Zip version

Unzip the downloaded file to any directory. From the application directory /logging-hub-[version]/bin/, start the Logging Hub with the command logging-hub.bat on Windows or ./logging-hub on Linux and MacOS. If the application starts correctly, you will see the * logging-hub-[version]-mule-application * default * DEPLOYED * line in the terminal or console. You are now ready to send your first log data and events to the Logging Hub!

Vagrant version

Start the application with the vagrant up command. During the first start, the Vagrant box from our Vagrant catalog might be downloaded, and this operation may take a while. Once Vagrant starts the virtual machine, you are ready to send your first log data and events to the Logging Hub! The Vagrant version includes the installation of the Logging Hub on Linux with a connection to Elastic and Kibana. See the Vagrant documentation for more information on this type of virtualization.

Docker version

Start the application with the docker run -d --net="host" --name logging-hub docker.integrationeye.com/logging-hub command. Once Docker starts the virtual machine, you are ready to send your first log data and events to the Logging Hub! The Docker version includes the installation of the Logging Hub on Linux with a connection to Elastic and Kibana. See the Docker documentation for more information on this type of virtualization.

The easiest way to try logging is to use the Logging Hub REST API to store data, e.g., using curl. The same APIs are used by individual Logging Probes.

curl --location --request POST 'localhost:8081/logging-hub-api/store-log-data' \
--header 'Content-Type: application/json' \
--data-raw '{
   "@timestamp":1620657000000,
   "@probeType":"java",
   "@exception":"java.lang.NullPointerException",
   "@rootException":null,
   "@stackTrace":"Exception in thread \"main\" java.lang.NullPointerException\r at com.example.myproject.Bootstrap.main(Bootstrap.java:14)",
   "@logPoint":"somewhere in the code it happened",
   "@messageType":"error",
   "@logLevel":"error",
   "@messageText":"Test log message",
   "@principal":"John Doe"
}'

The call example is simplified and does not contain all applicable call parameters. For example, it is possible to use the @extraData attribute to send any data (a map of key:value pairs) to the Logging Hub (these are then automatically propagated to Elastic or other system), @applicationName, @serverName and @serverIp; Logging Hub REST API can be secured using Basic Authorization, etc. All setting options and API attributes are described in the documentation.
However, if you want to log directly from your applications, then it is better to use the Logging Probes system. This way, you won't have to know the Logging Hub REST API, and you won't have any problem upgrading to newer versions and modifying direct calls of this API.

All versions of the Logging Hub available for downloading offer logging to a file located in /logging-hub-[version]/logs/logging-hub-probes-data.log. If the API call from the previous step was successful, you should see the following record in this file.

2021-05-10 14:30:00.000+02:00 [java] ERROR - {"@timestamp":1589992200000,"@probeType":"java","@exception":"java.lang.NullPointerException","@rootException":null,"@stackTrace":"Exception in thread \"main\" java.lang.NullPointerException\r at com.example.myproject.Bootstrap.main(Bootstrap.java:14)","@logPoint":"somewhere in the code it happened","@messageType":"error","@logLevel":"error","@messageText":"Test log message","@principal":"John Doe"}

Vagrant and Docker versions

In these versions, in addition to the log file logging-hub-probes-data.log, it is also possible to see the logged records in Elastic and Kibana (note that thanks to the built-in Logging Module, the Logging Hub can save one log event to multiple configured destinations at the same time). Elastic runs on http://localhost:9200/, and you can log in to Kibana via http://localhost:5601/. Use the link below to go directly to the Kibana dashboard.

http://localhost:5601/app/kibana#/dashboard/206a1450-c1d1-11ea-9299-0d50b3b947cd?_a=(description:'Test%20dashboard.%20Send%20more%20log%2Fevents%20to%20the%20Logging%20Hub%20to%20see%20them%20here.%20Add%20new%20visualizations...%0ARemember:%20this%20installation%20uses%20Demo%20license%20with%20limited%20calls.%20After%20the%2050th%20call,%20restart%20is%20necesary;%20then,%20it%20is%20possible%20to%20make%20another%2050%20calls%20%2F%20requests.',filters:!(),fullScreenMode:!f,options:(hidePanelTitles:!f,useMargins:!t),query:(language:kuery,query:''),timeRestore:!t,title:'Logging%20Hub%20Dashboard',viewMode:view)&_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-5y,to:now))

Visit Observability/Logs page in Kibana to see raw data logged using the Logging Hub (keep in mind that with @extraData attribute, you can log any map of key:value pairs). Use the link below to go directly to the Observability/Logs page.

http://localhost:5601/app/logs/stream?flyoutOptions=(flyoutId:YTm2SHMB08A_kUBL3yHq,flyoutVisibility:hidden,surroundingLogsId:!n)&logPosition=(end:now,position:(tiebreaker:1,time:1589997200000),start:now-5y,streamLive:!f)

Connect Logging Probes

Log anything you need directly from your applications. Download the Logging Probe according to the programming language used in your application and send the data to the Logging Hub. For code examples, settings, and other information, see the documentation for each Logging Probe.

Create your own dashboards in Kibana

Add your own dashboards and charts to enrich our demo in Kibana. See the online demo to find out what data can be collected using the Logging Hub. Point your on-prem Logging Hub to another Kibana and Elastic installation, or use a different connector from the Logging Module and send logs and events to completely different systems.

Learn more about Logging Hub and Logging Module

Learn what the Logging Hub and Logging Module can do, what their configuration options are, and how to best use them. For more information, see the documentation or FAQ. Feel free to ask us anything, we are here to help you!

Log everything possible!

This is not just a phrase; you can really log everything possible. A large amount of logs will help you detect errors and problems in applications, infrastructure, and it will inform you preventively about an emerging problem before your customer or user reports it.