v0.14 - Choices hot reload 🔥

Description

This is a major feature release and a first one created with active and effective contributions from @poludov (thanks mate!). The main feature is the AnaLog’s ability to automatically reload and apply changes to choices configuration just on-the-fly, i.e. without application restart. But apart of it, several other fixes and improvements have been included into this version.

Changes

• Provide choices configuration auto-reload
• Fix popups disappearing
• Upgrade to JDK 14
• Improve jUnit integration
• Fix 'Log not found' popup after v0.12.1
• Log record level is always detected as TRACE
• Some other helpful improvements (like integration with Travis CI and SonarQube).

ℹ️ See also v0.14 milestone.

Upgrading

If you’re upgrading your existing AnaLog instance, the following steps are required for this version to work:

1. Stop the application.

2. Replace analog.jar with the new one from the distribution archive (see download links below).

3. In analog or analog.bat file, replace the line:

   DEFAULT_JVM_OPTS="-XX:MaxMetaspaceSize=128M -XX:MaxHeapSize=256M -Dspring.config.additional-location=file:$APP_HOME/config/choices.yaml"

   with the following:

   DEFAULT_JVM_OPTS="-XX:MaxMetaspaceSize=128M -XX:MaxHeapSize=256M"

   (i.e. remove spring.config.additional-location JVM option)

4. In application.yaml file, add the following section:

   choicesSource:
     location: ${APP_HOME}/config/choices.yaml
     autoReloadEnabled: true

5. Start the application with analog[.bat] script.

If you’re installing AnaLog from scratch, see Installation & Usage section of README file.

Feedback

If you have any problems or just curious about some things around AnaLog, let us know by submitting an issue.

v0.12.1 - Fixes and upgrades

Description

This is an intermediate release aimed to better environment compatibility and stability of the application.

Changes

• compatibility with Java 13 runtime environment
• upgrading to Spring Boot 2.2.0.RC1
• upgrading to Gradle 5.6.2
• updating Docker deployment Gradle task
• creating a draft of automated distribution script
• some internal cleanups and fixes

Upgrading

Because the release affects the distribution structure, it is recommended to fully replace the previous installation with the new one. Though the updating of both lib/analog.jar and startup script should also be enough.
If you're just installing AnaLog from scratch, please follow usual Installation Instructions.

Log Access Restriction & Basic i18n

Release notes

See v0.12 Release Notes in Wiki.

Fixed issues

• #20
• #22
• and a couple of others not submitted to Github.

Environment changes

This version requires Java 12 to run.

Installation

See Installation & Usage instructions in README

v0.11 - Java 11 & Container logs support

Release notes

See v0.11 Release Notes in Wiki.

Fixed issues

• #15
• and some others not submitted to Github.

Installation

See Installation & Usage instructions in README

v0.10.1 - Bugfixes and refactoring

This is a bug fix release primarily based on #12 issue. It also brings an excessive refactoring of AnaLog's agent logic to solve some problems with watching similar logs on similar servers.

During the preparation of this release the application was tested to run on JRE 10.

ℹ️ To update your installation just replace analog.jar with the one attached to this release.

v0.10 - 'Download current log' feature

This release of AnaLog is aimed to shorten the gap between browser capabilities and real users' demands. While AnaLog was designed with certain browser restrictions in mind, it is quite obvious that ability to work with whole (usually big) log files is essential for day-to-day tasks. That is why AnaLog introduces this new feature - log file downloading directly from browser.

There are several changes to highlight:

• From this version on the application requires Java 9 as its runtime environment.

• Download current log button is now available for any log (not plains only) and click on it does not trigger
  downloading immediately anymore - instead a new 'Control Check' dialog is shown where:

  • Current log's node, path, size and last modified timestamp are displayed;
  • Download button is located along with its variants for downloading just last part of the log (50KB, 500KB, 5MB, 50MB, 200MB - depending of current log size);
  • Dropdown select is displayed to choose a specific member of composite log (in case of latter only);
  • Last error (if any) occurred while fetching log details (e.g. HTTP 404 Not Found, HTTP 503 Unavailable etc).

• Host and ports of cluster properties are now set separately. There are 2 kind of ports to specify:

  1. Agent port - a port to use by AnaLog server instance to support remote log monitoring;
  2. Server port - a port to use by user browser and by other servers for downloading log files from agent
     instances.
     This port is not required and by default equals to server.port of current AnaLog instance.

• clusterNodes param has been renamed to nodes as well as its address property has been renamed to host as it doesn't contain port number anymore.
  For example, if your configuration looks like:

clusterNodes:
  - name: alpha
    address: alpha.example.com:7801

then it should be rewritten as:

nodes:
  - name: alpha
    host: alpha.example.com
    agentPort: 7801
    serverPort: 8080    # may be omitted if equals to 'server.port'

• Added /download resource to AnaLog's server HTTP API:

  • HEAD /download returns content length and last modified timestamp of specified file even if it resides on
    remote node;
  • GET /download returns the specified file itself (as an attachment in order to facilitate streaming
    downloading). This also works transparently even for files on remote nodes of AnaLog.

  The new resource is designed to be used in various ways:

  • By web client application (in browser) to start file downloading via dedicated button on the control panel;
  • By other servers to retrieve files from agents in previous scenario;
  • By end users themselves to download frequently used files (e.g. by making a browser bookmark).

• Every log choice is now provided with label containing its 'type' (local, remote, composite) and list of its nodes.
  This is a groundwork for future support of remote plain logs and composite log configuration refactoring.

• Start scripts were completely remade and now the process stays active until get a signal from OS to shutdown. Many OS specifics were also accounted.

АнаЛог v0.8: открытый пилотный релиз

🇬🇧 🇺🇸 This is a trial release aimed at testing by Russian speaking users. Please let me know if you'd like to take a part in it and thus need for English version of installation manual.

Инструкция по установке

1. Распаковать архив в любую директорию целевого сервера;
2. Перейти в директорию распаковки;
   Убедиться, что в переменной окружения JAVA_HOME прописан путь к Java версии 8. Если ее нет, то прописать ее вручную в скрипт запуска run.sh (*nix) или run.cmd (Windows).
   Также на *nix системах выдать права на запуск скрипта run.sh текущему пользователю (chmod).
   При необходимости поменять умолчательные хост и порт в первых строках файла application.yaml.
3. Запустить скрипт run.sh (или run.cmd на Windows).
4. Открыть в браузере адрес сервера (например, http://localhost/).

✅ После этого в браузере должен будет выводиться (и обновляться) лог самого приложения - файл console.log, расположенный в той же директории.

ℹ️ Дополнительные сведения о настройке приложения см. в Wiki

AnaLog v0.6

This is mostly internal (and by the way the first public) release of AnaLog. It's main goal is to fix application's basic structure (primary framework, build system, version control system, etc). That is why this release is not shipped neither with any download'able binaries nor with proper documentation. If you find it missing please file an issue or (better) keep watching for upcoming v0.7 release.