---
schema_version: "1"
id: 111fa87911db19125e528986e325c502612d65e896a717ccf1240edc6a9ab574
title: Migrate Log Forwarding Before Upgrading Runtime Fabric
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-fabric/latest/migrate-log-forwarding.md
canonical_url: https://docs.mulesoft.com/runtime-fabric/latest/migrate-log-forwarding
source_site: docs.mulesoft.com
content_type: documentation
content_hash: d27993ae68c9b269aa899ecff1b818321aff8dfbe59f79fb5e65e7cce495545e
description: MuleSoft Documentation Site
release: "3.0"
latest: true
---
---
product: Runtime Fabric
version: 3.0
is-latest-version: true
---

# Migrate Log Forwarding Before Upgrading Runtime Fabric

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

> [!IMPORTANT] If you are currently using the log forwarder DaemonSet, you must complete these steps
> before upgrading Runtime Fabric to version 3.0.0. Failure to complete these steps may result in
> log forwarding disruption.

Starting with Runtime Fabric agent version 3.0.0, the DaemonSet-based log forwarding mechanism has
been removed. Log forwarding now occurs exclusively through application sidecar containers, which
provides better isolation, improved resource management, and simplified operations.

If the log forwarder DaemonSet is running on your cluster, complete these steps before upgrading:

1.  [Enable Application-Scoped Log Forwarding](#enable-app-scoped-log-forwarding)

2.  [Redeploy Applications Using Legacy Log Forwarding](#redeploy-apps-legacy-log-forwarding)

3.  [Remove the Log Forwarder DaemonSet](#remove-log-forwarder-daemonset)

4.  [Verify Migration](#verify-log-forwarding-migration)

## Enable Application-Scoped Log Forwarding

This setting is enabled by default on most Runtime Fabric instances. However, if it was previously
disabled, you must re-enable it using the Runtime Fabric API:

```bash
curl -X PATCH \
  -H 'Authorization: Bearer {authToken}' \
  -H 'Content-Type: application/json;charset=UTF-8' \
  -H 'Accept: application/json, text/plain, */*' \
  https://anypoint.mulesoft.com/runtimefabric/api/organizations/{orgId}/fabrics/{fabricId}/logforwarding/appScoped?enabled=true
```

Replace `{authToken}`, `{orgId}`, and `{fabricId}` with your specific values.

## Redeploy Applications Using Legacy Log Forwarding

All applications currently forwarding logs through the DaemonSet must be redeployed. This switches
them to use the sidecar container for log forwarding. You can trigger a redeployment by making any
update to the application in Runtime Manager, or by using the Runtime Manager API.

## Remove the Log Forwarder DaemonSet

After all applications are using the new sidecar-based log forwarding, remove the legacy DaemonSet
by calling the Runtime Fabric API:

```bash
curl -X PATCH \
  -H 'Authorization: Bearer {authToken}' \
  -H 'Content-Type: application/json;charset=UTF-8' \
  -H 'Accept: application/json, text/plain, */*' \
  https://anypoint.mulesoft.com/runtimefabric/api/organizations/{orgId}/fabrics/{fabricId}/logforwarding \
  -d '{"anypointMonitoring": false}'
```

Replace `{authToken}`, `{orgId}`, and `{fabricId}` with your specific values.

> [!NOTE] Disabling the DaemonSet doesn’t impact log forwarding to Anypoint Monitoring via the
> sidecar containers. Your applications will continue to forward logs normally after completing
> these steps.

## Verify Migration

After completing the previous steps, verify that:

- All applications are running and forwarding logs successfully

- The `am-log-forwarder` DaemonSet is no longer present in your cluster

- Application logs are visible in Anypoint Monitoring

## See Also

- [Enable and Configure Log Forwarding](https://docs.mulesoft.com/runtime-fabric/latest/use-anypoint-monitoring#logs)

- [Upgrading Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/upgrade-index)