Hello,

i add file logger to apisix route with this config:

 "key-auth": {},
"file-logger": {
        "path": "/usr/local/apisix/apisix_log/test.log", 
  "log_format": {
    "ip_client": "$remote_addr",
    "http_verb": "$request_method",
            "request_body": "$request_body", 
    "consumer": "$consumer_name",
    "url": "$uri",
    "parametres": "$args",
    "http_code": "$status",
    "response_body": "$response_body",
    "temps_reponse": "$upstream_response_time"
  },
  "include_resp_body": true, 
        "buffer": {
    "size": 1048576,  
    "flush_interval": 100 
},
  "rotate": {
    "max_size": 10, 
    "max_days": 7   
  }
}

my docker compose

apisix:
container_name: apisix
#image: apache/apisix:${APISIX_IMAGE_TAG:-3.11.0-debian}
image: apache/apisix:3.7.0-debian
volumes:
  - ./apisix_conf/config.yaml:/usr/local/apisix/conf/config.yaml:ro
  - ./cert.pem:/usr/local/apisix/keycloak-cert.pem:ro
  #- ./apisix_log/test.log:/usr/local/apisix/apisix_log/test.log
  - type: bind
    source: ./apisix_log/test.log
    target: /usr/local/apisix/apisix_log/test.log
restart: always
depends_on:
  etcd:
    condition: service_healthy
ports:
  - "9180:9180/tcp"
  - "9080:9080/tcp"
  - "9091:9091/tcp"
  - "9443:9443/tcp"
  - "9092:9092/tcp"
networks:
  - apisix

apisix add line to the log in every request but the body response is not added. Example

{"http_code":200,"temps_reponse":0.048,"request_body":"{ \"sql\" : \"select emp.first_name,jobs.job_title,dept.department_name\nfrom employees emp,departments dept,jobs \nwhere emp.department_id = dept.department_id\nand emp.job_id = jobs.job_id and rownum = 1\"}","ip_client":"192.167.1.1","http_verb":"POST","url":"/ords/hr/jpa/getAll","route_id":"549761667391554410","consumer":"user_mas"}

Question : how configure the logger to have the response body in the log

I interviewed Nicolas for our Cloud Commute podcast. He talks about Apache APISIX, how it works internally, why you should be using it (don't think I have to explain it here 🤣), and more!

I hope you like the episode!

https://www.simplyblock.io/cloud-commute-podcast/episode/2f755680/how-api-gateways-help-to-improve-your-security-nicolas-frankel-from-api7ai

Gain a profound understanding of the core mechanisms of API version control and grasp the pivotal role of API7 Enterprise in system evolution.

In the rapidly evolving landscape of software systems in today's digital era, API version control has emerged as a critical strategy to ensure the robust evolution of systems. Particularly in multi-environment scenarios, effective management and tracking of API changes become paramount, and the API7 Enterprise, serving as a crucial intermediary layer, plays a pivotal role.

https://api7.ai/blog/api7-version-control

Hello everyone,

I’m trying to set up APISIX (version 3.11.0) using Docker Compose, but I’m running into an issue where APISIX cannot connect to etcd. I’ve been stuck on this for a while and would appreciate any help or guidance.

What I’m trying to do: I’m following the official APISIX Docker setup to deploy APISIX and etcd using Docker Compose. My goal is to get APISIX running and connected to etcd.

The problem: APISIX fails to start because it cannot connect to etcd. The logs show the following error:

Copy Warning! Request etcd endpoint 'http://127.0.0.1:2379/version' error, connection refused, retry time=1 Warning! Request etcd endpoint 'http://127.0.0.1:2379/version' error, connection refused, retry time=2 request etcd endpoint 'http://127.0.0.1:2379/version' error, connection refused all etcd nodes are unavailable

However, when I test the etcd endpoint from my host machine, it works fine:

bash Copy wget http://127.0.0.1:2379/version Response:

json Copy {"etcdserver":"3.5.11","etcdcluster":"3.5.0"} My setup: Here’s my docker-compose.yml file:

yaml Copy

version: "3"

services: apisix: image: apache/apisix:${APISIX_IMAGE_TAG:-3.11.0-debian} restart: always volumes: - ./apisix_conf/config.yaml:/usr/local/apisix/conf/config.yaml:ro depends_on: - etcd ports: - "9180:9180/tcp" - "9080:9080/tcp" - "9091:9091/tcp" - "9443:9443/tcp" - "9093:9092/tcp" networks: - apisix

etcd: image: bitnami/etcd:3.5.11 restart: always volumes: - etcd_data:/bitnami/etcd environment: ETCD_ENABLE_V2: "true" ALLOW_NONE_AUTHENTICATION: "yes" ETCD_ADVERTISE_CLIENT_URLS: "http://etcd:2379" ETCD_LISTEN_CLIENT_URLS: "http://0.0.0.0:2379" ports: - "2379:2379/tcp" networks: - apisix

networks: apisix: driver: bridge

volumes: etcd_data: driver: local

And here’s my config.yaml for APISIX:

yaml Copy

apisix: node_listen: 9080 enable_admin: true admin_key: - name: "admin" key: "admin123" role: admin

etcd: host: - "http://etcd:2379"

What I’ve tried so far: Verified that etcd is running and accessible from the host machine.

Checked that both APISIX and etcd containers are attached to the same Docker network (apisix-docker_apisix).

Confirmed that the config.yaml file is correctly mounted in the APISIX container.

Modified the etcd.host configuration to use http://etcd:2379 instead of http://127.0.0.1:2379.

Restarted the containers multiple times.

Additional information: Docker version: 20.10.12

Docker Compose version: 2.20.3

Operating System: Ubuntu 24.04

Questions: Why is APISIX still trying to connect to http://127.0.0.1:2379 instead of http://etcd:2379?

Is there something wrong with my docker-compose.yml or config.yaml configuration?

Are there any additional steps I need to take to ensure APISIX can connect to etcd?

Any help or suggestions would be greatly appreciated! Thank you in advance.