FAQ

Our product contains 3 basic modules: Integration Eye™ Proxy Module (IPM), Integration Eye™ Logging Module (ILM) and Integration Eye™ Security Module (ISM). It also includes the Integration Eye™ Logging Hub application (which includes the Logging Module) and a set of Logging Probes designed to easily send event logs directly from your applications to the Logging Hub.

Any Integration Eye™ module or Logging Hub can run on your hardware, on-prem or in your private cloud.

in development We are currently developing an on-demand (SaaS) version of the Logging Hub, which will enable you to start logging any events very quickly without installing the Logging Hub on-prem component of Integration Eye™.

The easiest way is to use Logging Hub and Logging Probes. Logging Hub can be downloaded and run in minutes. With Logging Probes, you can then easily and efficiently send log events directly from your software (it is also possible to call the Logging Hub REST API to skip the Logging Probes).

Yes - both vertically and horizontally. In the case of the on-demand (SaaS) version, it will be done automatically in our cloud.

It depends on what exactly you need and what type of deployment you prefer, on-prem (private cloud) or on-demand (SaaS).

on-prem (private cloud) version - if all you need is event logging, then it is better to use Logging Hub and Probes. If you need, for example, to secure your API and services or use proxy on your network to transform data, etc., then it is better to use one of the examples (showcases) in the module documentation and then extend and configure it (samples can be downloaded, easily run and edited). Our modules have a really large number of functions, and sometimes it is not easy to design and configure everything properly, so if you have requirements and a goal, do not hesitate to contact us! We often perform analysis, configuration and installation of Integration Eye™ modules for our customers in their environment.

on-demand (SaaS) version in development - this version of the deployment offers the possibility to log events sent using Logging Probes directly from your software. It is then possible to visualize your logs and create dashboards and reports.

If you use an Offline license, then internet access is not required. If you use an Online (on-prem) license, then you need Internet access to validate the license online on our cloud during the start-up. However, all you have to do is to allow access to our validation cloud at https://api.integrationeye.com; nothing will be sent anywhere else. See what is the difference between Online and Offline (on-prem) licenses.

Yes - if the application sends data via HTTP protocol. All you have to do is direct the data flow to the Proxy Module with Logging Module, use the Logging Hub or a separate Logging Module. To redirect data, it is advisable to use, eg., Apache or Nginx. There are many options, so do not hesitate to contact us!

Connectors for RabbitMQ, HTTP (Elastic, Kibana, PRTG Network Monitor etc.) and File are available; other ones are in development. Let us know if you need any.

All of them - Logging Module contains a templating system and build-in connectors, thanks to which it is possible to transform log events into the correct format and save them in the correct storage for the given dashboard. For example, try the Kibana dashboard which can be downloaded with Vagrant and Docker versions of the Logging Hub.

You can log anything that comes through the HTTP protocol. With the help of Logging Probes, you can even log any data from the application (but you need to have access to the source code of the application). Neither the Logging Module nor Logging Hub limit you in what you can log. We are also working on the ability to log and prox data directly from the TCP/IP protocol.

There is no need to change your code when using the Logging Module. It collects data directly from HTTP traffic or takes it from Proxy Module traffic.

In case of Logging Hub and Logging Probes, you need to be able to interfere with the code of your application. For example, for Java application, you would need to add a small library (Java Logging Probe) to the classpath of the application, configure and call the appropriate .log() or .logAsync() method from this library (it works similarly with Logging Probes for other languages). Nothing more is needed, and it's very easy.

If the Logging Module that collects data is unavailable, then nothing happens, and your application is not affected. As soon as the Logging Module starts up again, all processes continue automatically. The same applies to the Logging Hub; if it is unavailable, it does not jeopardize the running of applications that send log events to it.

All components and modules of Integration Eye™ need Java Runtime Environment (JRE) version 8 or 12. Separate modules also need Mule Runtime version 4.2+. Logging Hub has both Mule Runtime and JRE integrated in downloadable versions. The recommended operating system is Linux, Windows or MacOS 64bit. However, all components of the Integration Eye™ can run on any operating system with the Java Runtime Environment (JRE).

Integration Eye™ is based only on best-in-class technologies, what guarantees speed, safety, and stability, including Java, Mule Runtime CE, Spring Framework, Java Messaging System, HTTP, OAuth 2.0 and Infinispan.

Hardware requirements are not demanding, but may vary depending on the load, amount of logged data, number of logins, generation of OTP codes, etc. The minimum for the Logging Hub is 1GHz CPU, 500MB disk space and 256MB RAM, but we recommend 2GHz CPU, 1GB disk space and 1GB RAM or more.

The structure of our software is based on and complements the structure of the Mule Runtime and has additional specific parts for running the Integration Eye™ modules and Logging Hub. Only the main components of Integration Eye™, instance configuration, startup scripts, and license locations are shown in the structure description below.

In most cases, yes. Our products have versions in X.Y.Z format where X is the major version, Y is the minor version, and Z is the bug-fix version. Changes of Z versions are always backward compatible, changes of Y versions are mostly backward compatible (however, minor incompatibilities may occur; for the user, it means minor changes in the XML configuration of Integration Eye™ modules). Changes of X versions are fundamental, so versions may not be backward compatible; however, we always try to make the new features fully backward compatible!

The upgrade can be performed either in the core of the system (i.e. Mule Runtime) or only in some applications (i.e. Integration Eye™ modules and Logging Hub). Mule Runtime needs to be reinstalled; you can always download the latest compatible version as part of the Logging Hub package or samples (showcases) in the documentation for individual modules.

Upgrade of Integration Eye™ modules - can be performed by installing the newer version of the module library (jar file) within your application in the apps directory (see the file structure of Integration Eye™).

Upgrade of the Logging Hub application - can be performed by downloading the latest version of Logging Hub from our site. Then, copy old version configuration files into your new Logging Hub installation in the apps/logging-hub-[version]-mule-application/ directory (the Logging Hub configuration files are described in documentation). Also, don't forget to return the old version license files of the Logging Hub (the new version of Logging Hub will only contain the Demo license). Then, start the new version of Logging Hub.

Upgrade of on-demand (SaaS) version in development - we will perform it automatically for you. You will just need to download the new versions of Logging Probes that you use.

Documentation for individual Integration Eye™ modules, Logging Hub and Logging Probes can be found at docs.integrationeye.com. The documentation also contains samples of downloadable modules (showcases), code snippets, instructions how to upgrade to new versions, etc. If you didn’t find the information you were looking for, contact us!

Yes - individual modules are available in the downloads section, as well as other parts of the Integration Eye™ - Logging Probes a Logging Hub.

It’s easy - if you come across any function you need that our product does not have, contact us, and we will gladly create it for you!

No - given the history of Integration Eye™ and its current deployment and distribution among customers, sharing the source code is undesirable. However, it is possible to download the source codes of individual Logging Probes.

Write us a message using the contact form and provide your Order reference ID or License ID (see the structure of the license file). We are currently developing a ticketing system for customers, please stay tuned!

Yes - see the license overview. With a Start-up license, you can even run Integration Eye™ modules or Logging Hub for free in a production environment; after registration, the license will be sent by email, and you can get started. It's easy.

On-prem licenses are always located on your server or computer in a designated directory conf/integrationeye-licenses/ (see file structure of Integration Eye™), where they are automatically loaded using the Integration Eye™ license manager (how to install a license?).

Offline (on-prem) license does not need to be validated online; moreover, with this type of license, the Integration Eye™ modules and Logging Hub can be run without the internet connection. Nothing will be sent outside your network. Any license is valid for 1 year and has to be replaced before it expires (by running the file). We will send you notification one month in advance together with a new license(s).

Online (on-prem) license in development has to be validated online to our cloud, and therefore, with this type of license, the Integration Eye™ modules and Logging Hub can be run only with the internet connection. However, all you have to do is allow access to our validation cloud at https://api.integrationeye.com; nothing will be sent anywhere else. The license will be automatically renewed on our cloud before it expires (subscription model). No action is required at your end.

License files are used only for the on-prem (or private cloud) deployment. The basic variants are Offline and Online (what is the difference between Online and Offline (on-prem) licenses?) The licenses are further divided into Production (used in production/non-production environment), Start-up (used in production/non-production environment) and Demo (used in non-production environment); see the license overview.

Copy the license file (or licenses) to the conf/integrationeye-licenses/ directory (see the Integration Eye™ file structure), where they are automatically loaded using the license manager during application startup. You will see the information and the number of loaded licenses in the logs/mule.log file, terminal or console during startup. License files are used only for the on-prem (or private cloud) deployment; the on-demand (SaaS) version uses the subscription model, and license files are not required.

*******************************************************************************
* Filename: integrationeye_20200617155258159.lic                              *
* Version: 1.0                                                                *
*-----------------------------------------------------------------------------*
* License ID: 3cb8ee20-7b16-4761-a7cc-e1700136e226                            *
* License is valid                                                            *
* Number of licenses: 1                                                       *
* Valid until: unlimited                                                      *
* Generated at: 2020-06-17T15:52:58.159                                       *
* License type: demo                                                          *
* License usage: non-production                                               *
* Max calls: 50                                                               *
* Issued for: Integsoft [Integration Eye Demo]                                *
* User: N/A                                                                   *
* User email: support@integrationeye.com                                      *
*******************************************************************************

License is one-line text file whose items are separated by a vertical bar (also called 'pipe'). Part of the file is encrypted, and if anything changes in it, the license manager detects the change and considers the license invalid. The information in the license file has only informative function for the user to better understand the purpose for which the license file can be used.

License file structure: version | license ID | type | usage | encrypted part | signature

Version:1.0|3cb8ee20-7b16-4761-a7cc-e1700136e226|demo|non_production|yW+fmrM5JtTlVwoTtm/jUGplBMjcszpNn8OwY/arXKLASoOK6+2cInLJcWPzK5QDdD+sOWBRDCMEt7JQLv+qRzZm/oIxDiN57XRcU1b2wS6simIggAqCHvzyq/LsG62RdcsMGcZXIo4uNJ957udNYd8xppxrZnCVxnLBHwIf5BGm0eeJtAAgaLFg7oDxh1ZeWbjLIBhpZvFb31ymJkYUELbWlQcBW/KAOIajlAVol265+jG2eaU7+YKGfHCbj0vwcSqummDL5Few53zcDa8yTj/6W5ICT459BYUQb1S2Yb6A78Ih6HzXmE01XrEoYM+Jp9wMf4AeI862njLQJE0Sr98QSAhvLioQcPZK1hHo5M8C5uyFGvOkUOU/J2ZYzwToizjDpEA7k9MEUJ2Vbfe7nA==|FG0pfLaicwC6Ei842w6lhc6y0BAz4AW3D9jCLobu+xd34jKdqmfn1PXZeos7U8AdrmpZGZtMjmtAHi8kiriiXcwFyUy8Y18PTTxt+TFB4atWnjL0GtOvVARIzwqNXdKwsixorG5WJLqgv+E1hTtZVVTSfvOoAmulF3bPCRGKk99PNKB1mrK2oNOayD3dO7VrxPR4ZUG/LFHl7tQSisB8p57+KH8oJNy+tCBMZhLuC7rOWjXUcdF4Sz8ak4uwUvHsRSmQvpCSmJtjVcE/yp3H1DAIrByvQeeWdue2H4yOJFpQ8Gs9rtjR00LeO83JHSNM6yoaq6MGvoMeuATl0/7GFQ==

No - all Integration Eye™ modules and Logging Hub are designed so that it is possible to use one license arbitrarily among them. It is thus possible to test all functions of all modules and the Logging Hub with a single license. However, the number of concurrently running instances of the modules and Logging Hubs must not exceed the total number of licenses in the license files loaded by the license manager during startup. You will see the information about licenses and their number during startup; you will be notified in case of exceeding the number of loaded licenses in the logs/mule.log file (see the file structure of Integration Eye™).

It is possible to use any on-prem license (see the license overview). The Logging Hub contains a Demo license which has a limit on the maximum number of calls without a restart and cannot be used in a production environment. You can also register and use Start-up license or purchase Production license that has no restrictions (you will also get our priority email support with it). Licenses can be replaced very easily.. If you do not want to log on-prem (or in private cloud), you can use Integration Eye™ on-demand (SaaS) version which contains on-demand Logging Hub.

Partly yes - it is possible to combine Offline (on-prem) and Online (on-prem) production license (what is the difference between Online and Offline (on-prem) licenses?). The license manager loads both types and includes them in the available licenses pool. You can also combine different Start-up licenses. However, it is not possible to combine Production, Start-up and Demo licenses with each other (i.e. to load 1x Production license and 3x Start-up licenses). In this case, the licenses will be loaded according to their priorities (see the priorities when loading licenses). Licenses that are not loaded by the license manager are ignored and do not apply; You will be notified of any problems in the logs/mule.log file, the terminal and / or the console during startup with a warning message.

Types of license files determine whether all of your production licenses are going to be stored in a single multi-license file or whether each production license will be stored in a separate single-license file(s). The built-in license manager can automatically load multiple license files from the license directory (see the the file structure of Integration Eye™), so if you are hesitant what solution to choose, mind that using single-license file(s) is safer. Non-production licenses always come in separate files, so you can distribute them to developers or test servers.

No - built-in license manager loads all available licenses immediately during startup (by default, the manager loads licenses from conf/integrationeye-licenses/, see the the file structure of Integration Eye™). It then assigns a license to each running application within the Mule Runtime if the application needs it. Once the assignment is complete, everything is ready for operation, during which nothing is validated, and therefore, it does not affect the speed.

Yes - to replace the license, overwrite the file in the directory designated for loading licenses. By default, Integration Eye™ license manager loads licenses from conf/integrationeye-licenses/, see the file structure of Integration Eye™.

Yes - but certain conventions need to be followed. The license file name must begin with integrationeye_ and must have .lic suffix. The rest of the text can be of your choice; by default, all new licenses have the date in their name in the following format: year month day hour minute second milisecond (e.g. integrationeye_20200513132100657.lic). Remember, do not change the contents of the license file as this may make it invalid.

During startup, each license loaded using the license manager is displayed in logs/mule.log file, terminal, or console (see the the file structure of Integration Eye™). If license manager finds any invalid or corrupted license file, it displays a corresponding warning; the same happens if any other problem occurs.

*******************************************************************************
* Filename: integrationeye_20200617155258159.lic                              *
* Version: 1.0                                                                *
*-----------------------------------------------------------------------------*
* License ID: 3cb8ee20-7b16-4761-a7cc-e1700136e226                            *
* License is valid                                                            *
* Number of licenses: 1                                                       *
* Valid until: unlimited                                                      *
* Generated at: 2020-06-17T15:52:58.159                                       *
* License type: demo                                                          *
* License usage: non-production                                               *
* Max calls: 50                                                               *
* Issued for: Integsoft [Integration Eye Demo]                                *
* User: N/A                                                                   *
* User email: support@integrationeye.com                                      *
*******************************************************************************

WARN  2020-02-17 08:19:01,252 [ForkJoinPool.commonPool-worker-1] [event: ] cz.integsoft.mule.license.manager.internal.DefaultLicenseManager: Failed load license /logging-hub-1.3.5/conf/integrationeye-licenses/integrationeye_20200101164423487.lic: Could not read license data from /logging-hub-1.3.5/conf/integrationeye-licenses/integrationeye_20200101164423487.lic! Provided license file /logging-hub-1.3.5/conf/integrationeye-licenses/integrationeye_20200101164423487.lic failed PKI signature verification!

Production licenses have the highest priority, followed by Start-up and finally Demo licenses. If Demo or Start-up licenses are mixed with Production licenses, then Demo/Start-up licenses are not taken into consideration. Finally, Start-up license takes precedence over Demo license. The license manager always disables license pools that are not used because of prioritizing; you will see a corresponding notification during the start, e.g., Disabling Demo license pool... .

on-prem (private cloud) version - you can use any of the offered licenses, i.e., Demo, Start-up or Production. Demo and Start-up are limited by the maximum number of calls, Production is unlimited and includes run optimizations and our priority email support (see the license overview).

on-demand (SaaS) version in development - this version does not require any licenses as it works on a subscription basis. When ordering this service, it is possible to select the required variant (number of log messages, size of history and other parameters).

Yes - by default, the license manager loads licenses from conf/integrationeye-licenses/ (see the the file structure of Integration Eye™). You can change this setting in the conf/wrapper.conf file where uncomment the line #wrapper.java.additional.18=-Dintegrationeye.licenses.folder=../conf/integrationeye-licenses and change the path and destination directory ../conf/integrationeye-licenses to the new one from which you want to load licenses.

Logging Hub is part of Integration Eye™ on-prem (or private cloud) and Integration Eye™ on-demand (SaaS) versions. Logging Hub version available for downloading includes a Demo license (which you can replace with another one at any time) and everything needed for storing logged data / events from Logging Probes (it is also possible to call the REST API of Logging Hub directly to omit Logging Probes, if needed). Logging Hub contains instance of the Logging Module, so it is possible to store the logs to files or to Elastic (or use another build-in connector of the Logging Module). Multiple versions are available for downloading, including the version with logging events to Elastic and displaying them in Kibana; individual versions are described in the downloads section. See the documentation for more information on the Logging Hub.

in development Logging Probes are pre-built libraries for various languages (Java, Javascript, Ruby, etc.) that you use in your application; by calling the library method, you can log any event to the Logging Hub (running on-prem or on-demand). See the documentation for more information on usage, setting options and individual Logging Probes.

Yes - download Logging Hub from the downloads section and follow a short procedure to start it and try it on-prem. Logging Hub has a wide range of settings because Logging Module is its integral part. Find more in documentation.

Not yet in development - but this way of deployment and operation is our goal, and we are working on it! If this mode of operation is indispensable for you, let us know, it will be great motivation for us!

Yes - in case you do not want to use Logging Probes, it is possible to call the Logging Hub REST API directly (e.g., using curl) and save log events / data this way.

curl --location --request POST 'localhost:8081/logging-hub-api/store-log-data' \
--header 'Content-Type: application/json' \
--data-raw '{
   "@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"
}'

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); Logging Hub REST API can be secured using Basic Authorization, etc. All setting options and API attributes are described in the documentation.

Yes - Logging Hub can be downloaded in the downloads section. Various formats, zip, Vagrant and Docker, are available for downloading.

So far, the following variants are available: Java, Scala and JRuby. However, we are working on other variants. Are you interested in a specific language? Contact us!

Yes - source code of individual Logging Probes can be downloaded.

Documentation is available at https://docs.integrationeye.com/logging-hub a https://docs.integrationeye.com/logging-probes.

Yes - Logging Hub uses Integration Eye™ Logging Module internally, and thus uses the same licensing system as this module. Thus, it is possible to use Demo, Start-up and / or Production licenses, see the license overview.

It may slightly vary depending on the language of the probe used. In general, probe configuration is done with the help of properties file, json, etc. It is also possible to use builder pattern for its configuration and use, as in Java Probe example below. You will find more information about each Logging Probe in dokumentation.

// If you have configuration file 'logging-probe.properties' on classpath, you can use
ProbeLogger logger = ProbeLoggerFactory.defaultLogger();

// If you want to use different properties file
ProbeConfig config = ProbeConfigBuilder.newInstance().from(Paths.get("custom.properties")).build(); 
ProbeLogger logger = ProbeLoggerFactory.customLogger(config);

// You can call probe using inline builder configuration
ProbeConfig config = ProbeConfigBuilder.newInstance().url("http://127.0.0.1:8081/logging-hub-api/store-log-data").build();
ProbeLogger logger = ProbeLoggerFactory.customLogger(config);

// Send the event to your Logging Hub (overloaded sync and async methods are available)
// You do not have to use CompletableFuture, but it is useful if you need to verify some data from the HTTP response returned from the Logging Hub.
CompletableFuture responseFuture = logger.logAsync(testMsg, LogLevel.info);

In the Logging Hub, it is possible to monitor the current status of all licenses using MBean. It is possible to connect to it, for example, via the jconsole application, which is a standard part of the Java JDK. After connecting to the local process MuleContainerBootstrap, you will find in MBeans tab the license pool cz.integsoft.integrationeye.license.pool which is used by the Integration Eye license manager. In this pool, you will find individual licenses, information about them and their count. Everything is divided into separate sections according to the type of license.

One of the main functions we are now developing are Integration Eye™ on-demand (SaaS) version, ticketing system for our users, Online (on-prem) license validation, TCP/IP proxy for Proxy Module; we are also working hard on the documentation for Integration Eye™ (docs.integrationeye.com)... We're also continuously developing functions required by our customers and incorporating them into individual modules. If you are interested in our product, but you lack some function, let us know, and we will prepare it for you!

Yes - We do not just offer a product that customers must try and use on their own. We work in a different way. We will be happy to advise and help you with everything; systems integration, logging and architecture are areas we have been working on for many years. Contact us, and we will gladly help you!

Any - If you are interested in the product, we are here to help you with its installation, setup and support. It all depends on the size and complexity of the project, what Integration Eye™ modules you will use and need. All problems are solvable, just contact us.

We are Integsoft - a company that has for many years been involved in Java software development, system (Mule runtime) and user (Keycloak SSO) integration, logging, tracking and transformation of data that are sent via integrated systems.

To help customers with tasks that, as we noticed, have been recurring over the years and that all customers need (with minor differences). Thus, after years of development, Integration Eye™ offers a comprehensive and reliable system that covers data transformation and proxying, logging (of literally anything you need, not just events or errors) and API security; see the properties of each module. Our customers love to use our products, and that is why in 2020, we decided to publish and offer our product to the general public through this website.

To offer customers a truly modular product, where they can use only the part that is necessary and useful for them. It reduces overheads, complexity of the configuration, likelihood of error, and so on.