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
Migrate Log Forwarding Before Upgrading Runtime Fabric
|
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:
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:
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:
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.
|
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. |



