How to set version¶
How to set version of LogMan.io¶
TeskaLabs LogMan.io product consists of two applications, LogMan.io and ASAB Maestro.
To run LogMan.io, you need to specify both the applications and their versions in the model.
define:
type: rc/model
services:
...
applications:
- name: "ASAB Maestro"
version: v24.30.01
- name: "LogMan.io"
version: v24.30.01
Versions and version files
The version refers to a specific version file in the Library.
Version v24.30.01 of ASAB Maestro application refers to /Site/ASAB Maestro/Versions/v24.30.01.yaml version file.
Version v24.30.01 of LogMan.io application refers to /Site/LogMan.io/Versions/v24.30.01.yaml version file.
define:
type: rc/version
product: LogMan.io
version: v24.30.01
asab_maestro_library: v24.29
versions:
lmio-collector: v24.25
lmio-receiver: v24.19.01
lmio-parsec: v24.30
lmio-depositor: v24.30
lmio-alerts: v24.24
lmio-elman: v24.22-beta3
lmio-lookupbuilder: v24.30
lmio-ipaddrproc: v24.30
lmio-watcher: v24.22
system-collector: v24.25
lmio-baseliner: v24.30
lmio-correlator: v24.30.01
library lmio-common-library: v24.30.01
To change the version of LogMan.io, simply rewrite versions of the applications in the model, save model and apply changes.
Choose existing versions and ensure compatibility
Select only version files that really exist in the Library.
Make sure that versions of ASAB Maestro and LogMan.io applications are compatible.
Custom versions¶
Avoid custom versions
LogMan.io consists of multiple services and we test their compatibility before every release. Versions distributed by TeskaLabs are tested and strongly recommended.
We cannot guarantee compatibility of services if combinations OTHER than those in the official version files are used.
For power users who skipped the warning, here are tips on how to customize versions:
Create new version file¶
In the Library, create new YAML file in /Site/<application>/Versions/ folder. Keep the required version file structure and specify versions of services. If no version specified for a service, latest version will be used by default. Set the name of the new file as a version of the application in the model.
Custom Version
Suppose that a new custom version file of LogMan.io application is named custom.yaml and it is placed in /Site/LogMan.io/Versions/custom.yaml in the Library.
To apply new version file, link it in the model and hit the "Apply" button.
define:
type: rc/model
services:
...
applications:
- name: "ASAB Maestro"
version: v24.30.01
- name: "LogMan.io"
version: custom
Override version in the model¶
To override version file from the model, use "version" key in the declaration of a service.
In this example, the version of instance asab-iris-1 will be set to v24.36. The version in the version file /Site/ASAB Maestro/Versions/v24.30.01.yaml will be ignored.
define:
type: rc/model
services:
...
asab-iris:
instances:
- node1
version: v24.36
applications:
- name: "ASAB Maestro"
version: v24.30.01
- name: "LogMan.io"
version: v24.30.01
Setting version per instance is not recommended
It is possible to set distinct version for each instance. We do not recommend this approach, though. Running multiple instances with distinct versions leads to serious errors in most of the services.
define:
type: rc/model
services:
...
asab-iris:
instances:
1:
node: node1
version: v24.36
2:
node: node1
version: v24.25
applications:
- name: "ASAB Maestro"
version: v24.30.01
- name: "LogMan.io"
version: v24.30.01