Loading

How to Forward Logs From Self Managed Flex Gateway to ELK

Date de publication: Sep 4, 2025
Tâche

GOAL

How to configure Elasticsearch logging for Self managed Flex Gateway

Étapes
MuleSoft support wont be able to help with the Log forwarding as per our Shared Responsibility model.
To help with the configuration, fluent-bit has a output for elasticsearch you can find more data about it here. You can use following config as an example.
Example: 
apiVersion: gateway.mulesoft.com/v1alpha1
kind: Configuration
metadata:
  name: elk-config
spec:
  logging:
    outputs:
    - name: es
      type: http
      parameters:
        host: "12345.eastus2.azure.elastic-cloud.com"
        port: "443"
        index: flex-application-logs-np
        type: doc
        HTTP_User: elastic
        HTTP_Passwd: 123
        tls: "on"
        tls.verify: "off"                
    runtimeLogs:
      logLevel: debug
      outputs: 
      - es
    accessLogs:
      outputs:
      - es
Disclaimer: This solution is provided as a reference for your own usage and is not to be considered a MuleSoft feature. This solution should be considered as a custom solution. The custom solution is not a Supported MuleSoft product.
Numéro d’article de la base de connaissances

001115335

 
Chargement
Salesforce Help | Article