top of page

Problem:

Analise client or server problem for which you need HTTP logs.

But what if the problem is intermittent or even rare for any particular users?

 

Solution:

Enable access logs on Tomcat, Apache,…

Find problematic request by specific markers (HTTP response code, server think time, response size, particular URI…), then restore conversation by session id:


5 views0 comments

Problem:

Data extracted with BiWhy from various sources like OS, BOBJ, CMS/Audit or other DBs, JMX, dumps, logs, configuration files, unformatted text files can be exported and analyzed in Excel, but this process is often time-consuming and inconvenient.

 

Solution:

BiWhy offers a range of analytical features that Excel does not support, such as handling over a million rows and dynamically hiding or showing columns…

Managing around 20 columns with long strings in Excel, for example, can be cumbersome, but BiWhy handles it effortlessly.

BiWhy includes many other valuable features, such as the ability to count events within specific time buckets (seconds, hours, days, etc.)



8 views0 comments

Problem:

Tens or hundreds of files, gigabytes in size, millions of lines, and thousands of error messages of varying severity across multiple processes and hosts, with clock skew between hosts.

Some errors are harmless, some are from unrelated workflows, and some are results of the original problem.

The challenge is to find the root cause.

 

Solution:

There are a few GLF viewers available, and some of them are decent.

However, they all lack certain essential functionalities or/and convenience features — such as workflow views, graphical representations/tables/trees/full text views, show/hide options for extended text/stacks, global stack view, filters, search, statistical analysis, and mining (flexible data extraction with conversion to tables for further analysis).

 

Example:

It took only couple minutes after opening GLF logs in BiWhy and checking the statistics table, which groups log messages by removing unique information from them.

The first most frequent error turned out to be irrelevant, but the second was our root cause.


9 views0 comments
bottom of page