# 'No configuration change, skipping sync to Kong' log message
**URL:** https://discuss.konghq.com/t/no-configuration-change-skipping-sync-to-kong-log-message/7069
**Category:** General
**Created:** [September 7, 2020, 8:33am UTC](https://discuss.konghq.com/t/no-configuration-change-skipping-sync-to-kong-log-message/7069 "2020-09-07T08:33:06Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Arnaud\_Hatzenbuhler](https://discuss.konghq.com/u/Arnaud_Hatzenbuhler)
#### Post date: [September 7, 2020, 8:33am UTC](https://discuss.konghq.com/t/no-configuration-change-skipping-sync-to-kong-log-message/7069/1 "2020-09-07T08:33:06Z")
Hello !
We are ingesting logs from ingress-controller to Elasticsearch, and we have this log
`no configuration change, skipping sync to Kong` which is going to stderr
I guess it’s meaning that the Ingress Controller has detected no changes in K8S resources and has nothing to do
I have 2 questions :
- Is it possible to remove this message ? If yes, how ?
- Why is it going to stderr ? It’s not really an error, right ?
Thanks in advance
---
### Author:  [@hbagdi](https://discuss.konghq.com/u/hbagdi)
#### Post date: [September 11, 2020, 11:43pm UTC](https://discuss.konghq.com/t/no-configuration-change-skipping-sync-to-kong-log-message/7069/2 "2020-09-11T23:43:22Z")
It is part of logging. It is being logged at the info level so you can use leveled-logging to exclude this from your search.
---
### Author:  [@Arnaud\_Hatzenbuhler](https://discuss.konghq.com/u/Arnaud_Hatzenbuhler)
#### Post date: [September 14, 2020, 8:14am UTC](https://discuss.konghq.com/t/no-configuration-change-skipping-sync-to-kong-log-message/7069/3 "2020-09-14T08:14:32Z")
As I see on this page : [https://github.com/Kong/kubernetes-ingress-controller/blob/master/docs/references/cli-arguments.md](https://github.com/Kong/kubernetes-ingress-controller/blob/master/docs/references/cli-arguments.md), you can configure to have more logs but not less
So, I guess the only solution is to filter on Elasticsearch/Kibana.
Still I have a question about an option : `--stderrthreshold`
In the documentation, it says : `logs at or above this threshold go to stderr.`
If the log is longer than 2 lines (by default) it goes in stderr, or if the log repeats 2 times it goes to stderr ? How does this parameter works ?
---
### Author:  [@hbagdi](https://discuss.konghq.com/u/hbagdi)
#### Post date: [September 21, 2020, 9:23pm UTC](https://discuss.konghq.com/t/no-configuration-change-skipping-sync-to-kong-log-message/7069/4 "2020-09-21T21:23:15Z")
With 0.10.0 version of the controller, logging has been re-written.
The new configuration options are here:
>
One of the goal is to simplify logging with the new changes.
---
### Author:  [@Arnaud\_Hatzenbuhler](https://discuss.konghq.com/u/Arnaud_Hatzenbuhler)
#### Post date: [September 24, 2020, 7:53am UTC](https://discuss.konghq.com/t/no-configuration-change-skipping-sync-to-kong-log-message/7069/5 "2020-09-24T07:53:04Z")
Thanks ! I’ll try this, but I think I can do what I wanted to do 🙂