Skip to main content

Is it possible to install HotJar in Maintenix?

Hi,

We do not have any history with Hot Jar. However since Maintenix uses common industry platforms, there have been many instances in the past of customers implementing overlay or monitoring technologies that work within or by accessing the JVM.

Thank you Robert, I understand that HotJar needs to be installed by pasting the HotJar code between the <head></head> tags of the website's HTML. So I am guessing that would not be possible for us to do. If you are aware of other products that allow you to capture user comments or experiences I would be interested in knowing more about them.

There are techniques within a proxy service, like a cache server or a load balancer, that would allow you to substitute and transform static information from the response of the application server before serving it to the end user’s browser. This would allow you to inject additional code in the headers.

There is an existing, although very limited, implementation of the end user tracking concept in Maintenix. One thing that is tracked is information regarding how many times end users encounter caught and uncaught exceptions in Maintenix. You can review this information in the UTL_ERROR_LOG table.

There is also potential to collect data through the Enabling and Configuring HTTP Access Logs. It can be parsed to analyze how users traverse through the system. The access logs as delivered with Maintenix are an implementation designed by Oracle Weblogic, and therefore they can be customized for different outputs by using Extended Log Format. Here is some prior work I’ve done to investigate this feature:

In addition to the reporting that is possible through Jaspersoft, there are the weblogic access logs. Mining these logs using a custom python solution, or with an available product on the market is something that many of our customers have adopted into their solutions.

These logs will track every HTTP request (GET or POST) by users in the system. The request against the report servlet will include the report name under the aTemplate URL parameter. The content of the access logs can be customized as well to meet your needs.

Please find this section: weblogic console in the section Environment > Servers > admin-server > Logging > HTTP

The Advanced Format can be changed from Common to Extended to add additional information to the log file. By default going from Common to Extended will append performance metrics (ms to deliver the requested resource).

The Extended Logging Format Fields is a series of terms where you can specify information you want returned in the access log. There are some fields that I believe you will find very valuable, including the originating IP address for the request (c-ip), and the URI query (cs-uri-query) which will isolate the URI parameters (aTemplate is the report name), and cs-uri-stem which will isolate the http path (/maintenix/servlet/report/generate is the URI you may want to track for menu driven reports).

Please see this article to situate yourself in the weblogic console:
https://docs.oracle.com/en/middleware/fusion-middleware/weblogic-server/12.2.1.4/cnfgd/web_server.html#GUID-872854AA-4C77-400F-A0D3-0F74E5133540

Please see this article for information about the Extended Logging Format Fields:
https://docs.oracle.com/en/middleware/fusion-middleware/weblogic-server/12.2.1.4/cnfgd/web_server.html#GUID-66DE589D-BA7E-44DF-A774-B3E361177DBF

For reference, here is the list that I tested:
date time cs-authuser c-ip cs-method cs-uri sc-status time-taken bytes s-ip c-dns s-dns sc-comment cs-uri-stem cs-uri-query ctx-ecid ctx-rid

Reply


Terms & ConditionsCookie settings