--- schema_version: "1" id: fa2710e37e240fe6e0ac3dd773dce6162081c7bf8da097ed97ef171017cd4224 title: Disabling Omni Gateway Log Output to Anypoint Platform collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/latest/conn-disable-logs.md canonical_url: https://docs.mulesoft.com/gateway/latest/conn-disable-logs source_site: docs.mulesoft.com content_type: documentation content_hash: 69565252f00ba15c793e91366a939118e9e01588c782a990d8c70a2fb8fecc84 description: MuleSoft Documentation Site release: "1.14" latest: true --- --- product: Omni Gateway version: 1.14 is-latest-version: true --- # Disabling Omni Gateway Log Output to Anypoint Platform > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Omni Gateway logging provides insights into startup, shutdown, API requests, API responses, policies, and Fluent Bit. Logging enables developers and administrators to identify and address issues or anomalies. However, disabling log output to Anypoint Platform might be necessary. Before disabling log output, consider the potential impact on troubleshooting capabilities. In some cases, it’s more appropriate to adjust the log verbosity level. You can disable sending the following logs to Anypoint Platform: - Runtime logs, including: - The startup and shutdown of Omni Gateway, Fluent Bit, and Envoy. - Deployed APIs and policies. - Possible misconfigurations of Omni Gateway or other errors. - Access logs, including: - The description of incoming interaction with Envoy over a period of time. - Incoming requests and responses for specific APIs. > [!NOTE] You can only disable logs sent to Anypoint Platform. Standard output (STDOUT) remains > unchanged. You disable sending logs to Anypoint Platform by using a local configuration file. The following tutorial describes how to create and deploy the file.

20%

25%

20%

20%

## Before You Begin Before configuring Omni Gateway log output, complete the following task: - Depending on your output, ensure that the service where you direct logs to is operational. For more information about log output services, refer to [Configuring Omni Gateway Output for Third-Party Services](https://docs.mulesoft.com/gateway/latest/conn-third-party-logs-config). ## Disable Anypoint Platform Log Output for Omni Gateway as a Linux Service 1. Create a YAML configuration file in your Omni Gateway configuration directory. For example: ```ssh sudo touch /usr/local/share/mulesoft/flex-gateway/conf.d/disable-logs-config.yaml ``` 2. In the configuration file, configure either or both `spec.logging.runtimeLogs.outputs.anypoint` and `spec.logging.accessLogs.outputs.anypoint` to `disabled`. The file resembles the following: ```yaml apiVersion: gateway.mulesoft.com/v1beta1 kind: Configuration metadata: name: logging-config spec: logging: runtimeLogs: logLevel: info outputs: anypoint: disabled accessLogs: outputs: anypoint: disabled ``` 3. Save the file. ## Disable Anypoint Platform Log Output for Omni Gateway in a Container > [!NOTE] If you have already added a volume for a folder with your Omni Gateway configuration > files, skip to step 4. 1. Press Ctrl+C to stop your Omni Gateway and any replicas. 2. Create a folder named `app` in the directory with your Omni Gateway configuration files. 3. Navigate to the `app` directory. 4. Create a new configuration YAML file named `disable-logs-config.yaml`. 5. In the configuration file, configure either or both `spec.logging.runtimeLogs.outputs.anypoint` and `spec.logging.accessLogs.outputs.anypoint` to `disabled`. The file resembles the following: ```yaml apiVersion: gateway.mulesoft.com/v1beta1 kind: Configuration metadata: name: logging-config spec: logging: runtimeLogs: logLevel: info outputs: anypoint: disabled accessLogs: outputs: anypoint: disabled ``` 6. Save the configuration file. 7. Restart your Omni Gateway with the configuration directory volume: - Docker - Podman ```ssh docker run --rm \ -v "$(pwd)":/usr/local/share/mulesoft/flex-gateway/conf.d \ -p 8080:8080 \ mulesoft/flex-gateway ``` > [!NOTE] Specify an optional name you want to assign to your Omni Replica by including the > following: `-e FLEX_NAME= \`. ```ssh podman run --rm \ -v "$(pwd)":/usr/local/share/mulesoft/flex-gateway/conf.d \ -p 8080:8080 \ docker.io/mulesoft/flex-gateway ``` > [!NOTE] Specify an optional name you want to assign to your Omni Replica by including the > following: `-e FLEX_NAME= \`. ## Disable Anypoint Platform Log Output for Omni Gateway in a Kubernetes Cluster To disable logging to Anypoint Platform: 1. Create a new resource using a YAML configuration file with the following example output configuration details: ```yaml apiVersion: gateway.mulesoft.com/v1beta1 kind: Configuration metadata: name: logging-config spec: logging: runtimeLogs: logLevel: info outputs: anypoint: disabled accessLogs: outputs: anypoint: disabled ``` 2. Configure either or both `spec.logging.runtimeLogs.outputs.anypoint` and `spec.logging.accessLogs.outputs.anypoint` to `disabled`. ## Disable Anypoint Platform Log Output for Omni Gateway in an OpenShift Cluster To disable logging to Anypoint Platform: 1. Create a new resource using a YAML configuration file with the following example output configuration details: ```yaml apiVersion: gateway.mulesoft.com/v1beta1 kind: Configuration metadata: name: logging-config spec: logging: runtimeLogs: logLevel: info outputs: anypoint: disabled accessLogs: outputs: anypoint: disabled ``` 2. Configure either or both `spec.logging.runtimeLogs.outputs.anypoint` and `spec.logging.accessLogs.outputs.anypoint` to `disabled`. ## See Also - [Configuring Omni Gateway Output for Third-Party Services](https://docs.mulesoft.com/gateway/latest/conn-third-party-logs-config) - [Message Logging Policy](https://docs.mulesoft.com/gateway/latest/policies-included-message-logging) - [Registering and Running Omni Gateway](https://docs.mulesoft.com/gateway/latest/conn-reg-run)