When using the Helm Chart to deploy Microcks, there’s a microcks.logLevelspec property you can set to DEBUG. Change it into your values.yaml file or as a command line argument using --set microcks.logLevel=DEBUG when redeploying the chart. This property changes both values for the main webapp and Async Miniong components.

When using the Microcks Operator, to deploy Microcks, the Microcks Custom Resource holds a microcks.logLevel property you can set to DEBUG. Change your CR to something like belob before re-deploying it:

apiVersion: microcks.io/v1alpha1
kind: Microcks
metadata:
  name: microcks
spec:
  version: 1.11.0
  microcks:
    url: microcks.m.minikube.local
    logLevel: DEBUG
  keycloak:
    url: keycloak.m.minikube.local

After the next operator reconciliation, the log level is changed in both the main webapp and the Async Minion component.

When using Docker or Podman Compose for running Microcks, you just have to add additional environment variables to the microcks and microcks-async-minoin containers.

You just have to edit the docker-compose.yml file to uncomment/enable the correct environement variables:

  app:
    # [...]
    container_name: microcks
    environment:
      # [...]
      - LOGGING_LEVEL_IO_GITHUB_MICROCKS=DEBUG
    # [...]

  async-minion:
    depends_on:
      - app
    # [...]
    container_name: microcks-async-minion
    environment:
      # [...]
      - QUARKUS_LOG_CONSOLE_LEVEL=DEBUG
      - QUARKUS_LOG_CATEGORY__IO_GITHUB_MICROCKS__LEVEL=DEBUG
    # [...]

Depending on the type of deployment (with or without asynchronous features), these container definitions may be distributed on different files.