# Disabling access logs for /status

**URL:** https://discuss.konghq.com/t/disabling-access-logs-for-status/516
**Category:** Questions
**Created:** [February 9, 2018, 12:29pm UTC](https://discuss.konghq.com/t/disabling-access-logs-for-status/516 "2018-02-09T12:29:27Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![pamiel](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/pamiel/32/153_2.png) [@pamiel](https://discuss.konghq.com/u/pamiel)
#### Post date: [February 9, 2018, 12:29pm UTC](https://discuss.konghq.com/t/disabling-access-logs-for-status/516/1 "2018-02-09T12:29:27Z")

</div>

I’m using the `/status` endpoint on the admin port as a readiness probe for Kong. The probe is triggered every 10 sec, which generates a lot of (useless) access logs generated just for this purpose.  
Is it possible to deactivate the access logs just for this `/status` endpoint ?

My understanding is that the `/status` is internally redirected to the `/nginx_status` internal endpoint, and the definition of this endpoint in the `nginx-kong.conf` file has the clause `access_log off`… but still, the access logs are there !

Did I missed something ?  
A bug?

Thanks !

---

<div class="post-metadata">

### Author: ![pamiel](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/pamiel/32/153_2.png) [@pamiel](https://discuss.konghq.com/u/pamiel)
#### Post date: [March 30, 2018, 5:41pm UTC](https://discuss.konghq.com/t/disabling-access-logs-for-status/516/2 "2018-03-30T17:41:03Z")

</div>

Hi,

Anyone from the Kong team or others having a feedback on this question?

Thanks 😉

---

<div class="post-metadata">

### Author: ![jeremyjpj0916](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/jeremyjpj0916/32/1388_2.png) [@jeremyjpj0916](https://discuss.konghq.com/u/jeremyjpj0916)
#### Post date: [April 1, 2018, 4:49am UTC](https://discuss.konghq.com/t/disabling-access-logs-for-status/516/3 "2018-04-01T04:49:48Z")

</div>

Are you using like kubernetes for your deployments? If so Why not use a check like so:

[https://www.tigraine.at/2017/01/19/configuring-kong-health-checks-in-kubernetes](https://www.tigraine.at/2017/01/19/configuring-kong-health-checks-in-kubernetes)

```auto
readinessProbe:                                                                                                                                                                                            
   exec:                                                                                                                                                                                                    
     command:                                                                                                                                                                                               
       - kong                                                                                                                                                                                               
       - health 

```

The article is a bit out of date regarding the /status behavior and its older problems but I still think using kong health is a great alternative. Might be what you want.