Tyk-syslog implementation

Hello @Page.
Elastic-search if finally ok,i am trying to work with fluentd now, but i am not able to print the log.

I show you my how i use it. i use helm chart for tyk and fkuentd.
tyk:

## Default values for tyk-headless chart.
## This is a YAML-formatted file.
## Declare variables to be passed into your templates.
## See Tyk Helm documentation for installation details:
## https://tyk.io/docs/tyk-oss/ce-helm-chart/
## Registry for all Tyk images - https://hub.docker.com/u/tykio

# Chart name override. Truncates to 63 characters.
# Default value: tyk-headless.name
nameOverride: "tyk"

# App name override. Truncates to 63 characters.
# Default value: tyk-headless.fullname
fullnameOverride: "tyk-h"

# These are your Tyk stack secrets will directly map to the following Tyk stack
# configuration:
secrets:
  # tyk.conf node_secret
  # tyk.conf secret
  APISecret: CHANGEME
  # If you don't want to store plaintext secrets in the Helm value file and would
  # rather provide the k8s Secret externally please populate the value below
  useSecretName: ""

redis:
  addrs:
    - tyk-redis-master.tyk.svc.cluster.local:6379
  pass: "zk8hzkdx3r"
  # Redis password
  # If you're using Bitnami Redis chart (e.g. bitnami/redis) please input
  # your password in the field below
  # pass: ""



  # Enables sentinel connection mode for Redis. If enabled, provide both
  # mandatory values for sentinelPass and masterName.
  # enableSentinel: false

  # Redis sentinel password, only required while enableSentinel is true.
  # For bitnami/redis the same password as Redis above
  # sentinelPass: ""

  # Redis sentinel master name, only required while enableSentinel is true.
  # For bitnami/redis typically redis-master
  # masterName: "redis-master"

  # By default the database index is 0. Setting the database index is not
  # supported with redis cluster. As such, if you have enableCluster: true,
  # then this value should be omitted or explicitly set to 0.
  storage:
    database: 0

# Choose the pumps backend for Tyk. [ "", "mongo", "postgres" ]
backend: "postgres"
mongo:
  # The mongoURL value will allow you to set your MongoDB address.
  # Default value: mongodb://mongo.{{ .Release.Namespace }}.svc.cluster.local:27017/tyk_analytics
  # mongoURL: mongodb://mongo.tyk.svc.cluster.local:27017/tyk_analytics
  # If your MongoDB has a password you can add the username and password to the url
  # mongoURL: mongodb://root:[email protected]:27017/tyk_analytics?authSource=admin

  # Enables SSL for MongoDB connection. MongoDB instance will have to support that.
  # Default value: false
  useSSL: false

# Postgres connection string parameters.
postgres:
  host: tyk-postgres-postgresql.tyk.svc.cluster.local
  port: 5432
  user: postgres
  password: "YR7bUylTuD"
  database: tyk_analytics
  sslmode:

gateway:
  # The hostname to bind the Gateway to.
  hostName: tyk-gw.local
  # When true, sets the gateway protocol to HTTPS.
  tls: false

  kind: Deployment
  replicaCount: 1
  containerPort: 8080
  image:
    repository: docker.tyk.io/tyk-gateway/tyk-gateway
    tag: v5.2.1
    pullPolicy: IfNotPresent
  service:
    type: NodePort
    port: 8080
    externalTrafficPolicy: Local
    annotations: {}
  # control:
  #   enabled: false
  #   containerPort: 9696
  #   port: 9696
  #   type: ClusterIP
  #   annotations: {}
  # Creates an ingress object in k8s. Will require an ingress-controller and
  # annotation to that ingress controller.
  ingress:
    enabled: false
    # specify your ingress controller class name below
    className: ""
    annotations: {}
      # kubernetes.io/ingress.class: nginx
      # kubernetes.io/tls-acme: "true"
    hosts:
      - host: chart-example.local
        paths:
          - path: /
            pathType: ImplementationSpecific
    tls: []
  #  - secretName: chart-example-tls
  #    hosts:
  #      - chart-example.local

  resources: {}
    # We usually recommend not to specify default resources and to leave this
    # as a conscious choice for the user. This also increases chances charts
    # run on environments with little resources, such as Minikube. If you do
    # want to specify resources, uncomment the following lines, adjust them
    # as necessary, and remove the curly braces after 'resources:'.
    # limits:
    #  cpu: 100m
    #  memory: 128Mi
    # requests:
    #  cpu: 100m
    #  memory: 128Mi
  securityContext:
    runAsUser: 1000
    fsGroup: 2000
  nodeSelector: {}
  tolerations:
    - key: node-role.kubernetes.io/master
      effect: NoSchedule
  affinity: {}
  extraEnvs:
    - name: TYK_GW_ENABLEHASHEDKEYSLISTING
      value: "true"
    - name: TYK_GW_ANALYTICSCONFIG_ENABLEDETAILEDRECORDING
      value: "true"
  ## extraVolumes A list of volumes to be added to the pod
  ## extraVolumes:
  ##   - name: ca-certs
  ##     secret:
  ##       defaultMode: 420
  ##       secretName: ca-certs
  extraVolumes: []
  ## extraVolumeMounts A list of volume mounts to be added to the pod
  ## extraVolumeMounts:
  ##   - name: ca-certs
  ##     mountPath: /etc/ssl/certs/ca-certs.crt
  ##     readOnly: true
  extraVolumeMounts: []
  mounts: []

# If pump is enabled the Gateway will create and collect analytics data to send
# to a data store of your choice. These can be set up in the pump config. The
# possible pump configs can be found here:
# https://github.com/TykTechnologies/tyk-pump#configuration
pump:
  # Determines whether or not the pump component should be installed.
  enabled: true

  replicaCount: 1
  image:
    repository: docker.tyk.io/tyk-pump/tyk-pump
    tag: v1.8.3
    pullPolicy: IfNotPresent
  annotations: {}
  resources: {}
    # We usually recommend not to specify default resources and to leave this
    # as a conscious choice for the user. This also increases chances charts
    # run on environments with little resources, such as Minikube. If you do
    # want to specify resources, uncomment the following lines, adjust them
    # as necessary, and remove the curly braces after 'resources:'.
    # limits:
    #  cpu: 100m
    #  memory: 128Mi
    # requests:
    #  cpu: 100m
    #  memory: 128Mi
  securityContext:
    runAsUser: 1000
    fsGroup: 2000
  nodeSelector: {}
  tolerations: []
  affinity: {}
  extraEnvs:
    - name: TYK_PMP_PUMPS_SYSLOG_TYPE
      value: syslog
    - name: TYK_PMP_PUMPS_SYSLOG_META_NETWORKADDR
      value: my-fluentd-aggregator.fluentd.svc.cluster.local:5410
    - name: TYK_PMP_PUMPS_SYSLOG_META_TRANSPORT
      value: "udp"
    - name: TYK_PMP_PUMPS_SYSLOG_LOG_LEVEL
      value: "6"
    - name: TYK_PMP_PUMPS_SYSLOG_META_TAG
      value: "tyk-pump"
    - name: TYK_PMP_DECODERAWREQUEST
      value: "true"
    - name: TYK_PMP_DECODERAWRESPONSE
      value: "true"
      
  extraVolumes: []
  ## extraVolumeMounts A list of volume mounts to be added to the pod
  ## extraVolumeMounts:
  ##   - name: ca-certs
  ##     mountPath: /etc/ssl/certs/ca-certs.crt
  ##     readOnly: true
  extraVolumeMounts: []
  mounts: []

rbac: true

and for fluentd:

helm install -f ./values-fluentd.yaml my-fluentd bitnami/fluentd --version 5.9.6 -n fluentd
Can you please help me with the configuration values file of fluentd and tell me if the side tyk-pump configuration is ok ?
For fluentd i dont know if i need to use the aggregator or the forwarder, it is confusing and i test to use both but the are not working…
Thanks in advance !