/
Post-Deployment Operational Guide

Post-Deployment Operational Guide

Page Contents:

LHO App Version Upgrade

Lakehouse Optimizer requires periodic upgrades to deliver new features, improvements and bug fixes. If a Blueprint representative has access to your environment, they’ll handle the upgrade for you. For those who prefer to upgrade themselves, Blueprint will notify you when a high-impact upgrade is pending and version details.

  1. SSH into your LHO VM

  2. Login as user that has sufficient permissions to update docker compose files, pull and deploy images.

  3. Navigate to the installation directory
    The command depends on where the files are located on your VM. For example:
    cd /opt/lho_install/

  4. Update Docker Compose Files

    1. Update docker-compose.yml
      Open the docker-compose.yml file in your preferred text editor. For example, run nano docker-compose.yml
      Update the image version to the one you plan to deploy.

      2025-11-25_10h03_11-20251125-180502.png

      Save file.

    2. Update forecaster-compose.yml
      Open the forecaster-compose.yml file in your preferred text editor. For example, run nano forecaster-compose.yml
      Update the image version to the one you plan to deploy.
      Save file.

  5. Pull and Deploy Updated Images
    Run the following command:
    docker-compose -f docker-compose.yml pull && docker-compose -f docker-compose.yml up -d && docker-compose -f forecaster-compose.yml pull && docker-compose -f forecaster-compose.yml up -d && docker system prune -a -f

 

Logs

Instantly check new log messages

To quickly check the logs of your LHO deployment you can use:

docker logs --tail <HOW MANY LINES OF LOG YOU WANT, E.G: 1000> bplm

If you want to constantly get new lines of logs as they spawn you can use the -f in the command above like this:

docker logs --tail 200 -f bplm

This will print the latest 200 lines of logs as well as keep printing new lines as they get logged. Press CTRL-C to exit this command when you’re done.

Check log files for historical information

To check more logs we recommend looking into your configured log location. Inside your docker-compose.yml you should see where the logs are actually stored. For instance:

docker-compose.yml

volumes: ... - /var/log/bplm:${LOG_DIR:-/var/log/bp-lakehouse-monitor} # THE LOGS ARE STORED IN /var/log/bplm

forecaster-compose.yml

volumes: - ./logs:/var/log/ # THE LOGS ARE STORED IN THE DIRECTORY WHERE THE YML FILE RESIDES, INSIDE A FOLDER CALLED log

LHO log files

LHO splits it’s logs according to certain App Modules. As such you’ll have logs for consumption: bplm-consumption.log, UC assessment logs: uc-assesment.log, processor logs: bplm-processor.log, and others.

The logs that you see when issuing docker logs are stored inside bplm.log. This is the master logfile where you can see all of the log messages from LHO (including ones that are part of consumption, processing, etc).

LHO has log rotation implemented so bplm.log will usually hold new log messages also viewable with docker logs. The older logs will be stored in the archived directory.

Forecaster log file

The forecaster writes it’s output to the cron.log file inside your logs folder.

Configure Support Alert Emails on LHO

LHO can send out alert emails which help you monitor the condition of your LHO Application. To receive such alerts from your system you need to:

  1. Configure notifications in your .env by adding the following information

    NOTIFICATION_EMAIL=<your email address: lho-monitoring@mycompany.com>

  2. Re-start your LHO container using this new configuration

    docker-compose -f docker-compose.yml up -d

Once this is done the email address you configured is set to receive notification emails from your LHO Application.

Renew Expired Certificates

  • If your LHO is set up to use the default LetsEncrypt SSL certification no action is needed. The certificates re-new on their own. Make sure that the HTTP port on the machine is accessible from the internet. The HTTP port is used only when certbot renews the certificates. The LetsEncrypt servers need to complete a challenge-response exchange with your server to assert ownership of your Domain. More info can be found in the LetsEncrypt docs here: https://letsencrypt.org/docs/challenge-types/#http-01-challenge.

  • If you’ve configured LHO to use SSL certificates you provide renew the certificates in the SSL provider you use and make sure you follow the documentation for generating a keystore and configuring LHO to use it once you have obtained the new SSL certificates. https://blueprinttechnologies.atlassian.net/wiki/x/CYDXrg