# GET /status HTTP/2.0" 200 2198 "-" "kong-ingress-controller/NOT\_SET"

**URL:** <https://discuss.konghq.com/t/get-status-http-2-0-200-2198-kong-ingress-controller-not-set/13532>\
**Category:** Questions\
**Tags:** kubernetes, kong-gateway\
**Created:** [May 12, 2025, 3:33pm UTC](https://discuss.konghq.com/t/get-status-http-2-0-200-2198-kong-ingress-controller-not-set/13532 "2025-05-12T15:33:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cesar\_Diaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/cesar_diaz/32/4904_2.png) [@Cesar\_Diaz](https://discuss.konghq.com/u/Cesar_Diaz)\
**Post date:** [May 12, 2025, 3:33pm UTC](https://discuss.konghq.com/t/get-status-http-2-0-200-2198-kong-ingress-controller-not-set/13532/1 "2025-05-12T15:33:25Z")

</div>

Hello I am getting this message in the gateway. I would like to know if the log entry `GET /status HTTP/2.0" 200 2198 "-" "kong-ingress-controller/NOT_SET"` is this a normal behavior for Kong Ingress Controller? meaning is this expected because the `/status` endpoint is an internal Kong endpoint rather than one that’s configured through Kubernetes Ingress objects?. If it is, is a recommend it way to filter out the NOT\_SET from the logs and the UI?