Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Deactivating logs and metrics transfer upon deployment or upgrade

Last updated: 2026-11-03

During engine deployment or upgrade, prevent logs and metrics from being sent to Talend Management Console for tasks executed in a Dynamic Engine environment.

Information noteNote: This procedure only applies to deployments and upgrades of a Dynamic Engine environment. You can revert these settings with a subsequent upgrade.

Before you begin

  • Your Dynamic Engine must have been deployed. If not, run this command to deploy it:
    helm install dynamic-engine -f <engine-id>-helm-values/<engine-id>-values.yaml oci://ghcr.io/talend/helm/dynamic-engine
    This is the default deployment, because the current customization is only needed on the Dynamic Engine environment side. For this reason no customization is configured for the Dynamic Engine instance.

About this task

By default, logs and metrics from tasks running in a Dynamic Engine environment are sent to Talend Management Console. You can deactivate this behavior at deployment or upgrade time by customizing the environment configuration.

Procedure

  1. In the Kubernetes machine, unzip the Helm deployment zip file previously downloaded.
  2. Create a custom values file to deactivate logs and metrics transfer from your Dynamic Engine environment. 
    cat <<EOF > $DYNAMIC_ENGINE_ENVIRONMENT_ID-custom-log-metrics-values.yaml
configuration:
  logging:
    publishToTalendCloud: false
  observability:
    componentMetricsFeatureEnabled: false
EOF
  3. Deploy the Dynamic Engine environment with logging and metrics transfer deactivated. 
    helm install dynamic-engine-environment-$DYNAMIC_ENGINE_ENVIRONMENT_ID -f $DYNAMIC_ENGINE_ENVIRONMENT_ID-values.yaml  \
 -f $DYNAMIC_ENGINE_ENVIRONMENT_ID-custom-log-metrics-values.yaml \
 oci://ghcr.io/talend/helm/dynamic-engine-environment \
 --version $DYNAMIC_ENGINE_VERSION
    Information noteTip: When changes are needed, you can update the content of the $DYNAMIC_ENGINE_ENVIRONMENT_ID-custom-log-metrics-values.yaml file and run helm upgrade to apply the changes:
    helm upgrade dynamic-engine-environment-$DYNAMIC_ENGINE_ENVIRONMENT_ID -f $DYNAMIC_ENGINE_ENVIRONMENT_ID-values.yaml  \
-f $DYNAMIC_ENGINE_ENVIRONMENT_ID-custom-log-metrics-values.yaml \
oci://ghcr.io/talend/helm/dynamic-engine-environment \
--version $DYNAMIC_ENGINE_VERSION
  4. Verify that logs and metrics transfer is deactivated in the environment configuration.
    1. Check the logging configuration: 
      kubectl get configmap -n qlik-processing-env-$DYNAMIC_ENGINE_ENVIRONMENT_ID \
global-configuration -ojsonpath="{.data['global-configuration\.json']}" | jq -r '.logging'

      Confirm that publishToTalendCloud is set to false.

    2. Check the observability configuration: 
      kubectl get configmap -n qlik-processing-env-$DYNAMIC_ENGINE_ENVIRONMENT_ID \
global-configuration -ojsonpath="{.data['global-configuration\.json']}" | jq -r '.observability'

      Confirm that componentMetricsFeatureEnabled is set to false.

Results

The Dynamic Engine environment is deployed with logs and metrics transfer deactivated. No execution logs or metrics will be sent to Talend Management Console for task runs in this environment until you re-activate this feature.

In Talend Management Console, the status of this environment becomes Ready, confirming that it is ready to run tasks or plans.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here