This is the documentation for Clover Club 12.0.
Documentation for the upcoming version Rampur 13.0 can be found here.

Legacy Server Logs

Owned by Jan Panoušek
Jun 14, 2024
2 min read

Redis Server Logs

Since the 7.0 Bijou release, clusters were typically running on Redis. In a Redis-based bare-metal solution, the Pricefx backend sends structured logs from standard output to Redis and the user can display these logs in the Pricefx UI. The log contains logs from all nodes.

  • Besides the standard log, there is also a performance log available, listing all the executed commands and their run time.

  • The Streams drop-down menu allows you to switch between partitions and jobs.

  • For filtering, use the Tailgrep field to apply the filter on the last 5,000 lines and the new lines. It supports regular expressions and is case insensitive. You can filter on node, logger, level, thread, username, message and stack. Filtering on Timestamp is not supported.
    For example, a commonly used filter is .*username.* which says "find all logs that contain username anywhere in them". You can replace "username" with anything you want to search.
    For more details see Regular expression syntax cheatsheet.

  • The full log can be downloaded in the JSON format. Open the file in your favorite JSON reader or transform it into a readable format with some tools. For example:

    cat log_*.json | jq -r ".logstash[].log | [.timestamp,.node,.logger,.level,.thread,.username,.message,.stack] | @csv" | sed 's/\\n/\'$'\n''/g' | sed 's/\\t/\'$'\t''/g' | less

  • If required, logging into Redis can be disabled in System Configuration (Logging & History section).

  • The minimum supported version of Redis is 6.0.

Logs before 7.0

This is the traditional way of logging before the 7.0 Bijou release. It is still available if your solution runs on a bare-metal server and you enable the option Disable logging to Redis in General Settings.

To view the server log file, navigate to Administration > Logs > Logs. The page shows the latest 300 lines and refreshes automatically every five seconds. The messages are displayed in reverse order, i.e., the latest one is on the top.

This is a log of only one node – see the URL to find out which one. It is highly likely that scheduled tasks (or other tasks you fire manually) are running on another node, and so you cannot see the log output. To see the log of other nodes, click the Node button and type in the node's name. Active nodes are listed on the Jobs & Tasks page.

If you need to review the full server log, use the Download button to get the complete log as a ZIP file.