# Kibana Setting "logging.dest" is deprecated can't be fixed **URL:** \ **Category:** Kibana\ **Created:** [December 10, 2021, 12:37pm UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424 "2021-12-10T12:37:00Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![KillianS](https://avatars.discourse-cdn.com/v4/letter/k/f6c823/32.png) [@KillianS](https://discuss.elastic.co/u/KillianS)\ **Post date:** [December 10, 2021, 12:37pm UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/1 "2021-12-10T12:37:00Z")
Hi all, We are facing an issue with Kibana 7.16.0 on Ubuntu 18.04. In Kibana log I can see a warning message ["warning","config","deprecation"],"pid":24471,"message":""logging.dest" has been deprecated and will be removed in 8.0. To set the destination moving forward, you can use the "console" appender in your logging configuration or define a custom one."}. In the upgrade assistant for ELK 8.0 we are facing the same message. To correct it seems we have to add this parameters : ```auto logging: appenders: file: type: file fileName: /var/log/kibana.log layout: type: pattern loggers: - name: plugins.myPlugin appenders: [file] ``` I'm starting with ELK and I don't know how to add this parameters, I try with a cURL but this does not solve the problem. In kibana.yml I removed logging.dest like this is mentionned in the picture. ![logging.dest](https://us1.discourse-cdn.com/elastic/original/3X/2/b/2b151e704c6a1d4a5d9105febfcb0e124e90dfbc.png) Could someone can help me to resolve this issue ? Thanks for your answer. ---
**Author:** ![rthl](https://avatars.discourse-cdn.com/v4/letter/r/9f8e36/32.png) [@rthl](https://discuss.elastic.co/u/rthl)\ **Post date:** [December 14, 2021, 2:10pm UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/2 "2021-12-14T14:10:56Z")
Hi, got the same problem. All changes in kibana.yml are ignored. I noticed that "logging.dest" is hardcoded in unit file "kibana.service". So what to do about that? Thanks ---
**Author:** ![KillianS](https://avatars.discourse-cdn.com/v4/letter/k/f6c823/32.png) [@KillianS](https://discuss.elastic.co/u/KillianS)\ **Post date:** [December 20, 2021, 2:21pm UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/3 "2021-12-20T14:21:32Z")
Hi all, Upgrading to 7.16.2 did not solve the problem. ---
**Author:** ![VamPikmin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vampikmin/32/22367_2.png) [@VamPikmin](https://discuss.elastic.co/u/VamPikmin)\ **Post date:** [December 24, 2021, 5:08am UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/4 "2021-12-24T05:08:54Z")
I added the parameters to kibana.yml but the critical warning is still present in Kibana UI ---
**Author:** ![KillianS](https://avatars.discourse-cdn.com/v4/letter/k/f6c823/32.png) [@KillianS](https://discuss.elastic.co/u/KillianS)\ **Post date:** [December 24, 2021, 7:41am UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/5 "2021-12-24T07:41:06Z")
Yes and I don't know if we have to pass this parameters in Kibana Console or with a cURL command. ---
**Author:** ![chouben](https://avatars.discourse-cdn.com/v4/letter/c/e495f1/32.png) [@chouben](https://discuss.elastic.co/u/chouben)\ **Post date:** [January 13, 2022, 9:33am UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/6 "2022-01-13T09:33:41Z")
You have to add it to the /etc/kibana/kibana.yml file. I noticed the default appender is required: > Jan 13 10:30:14 stvjustxelk001 kibana[7812]: FATAL Error: [config validation of [logging].root]: "default" appender required for migration period till the > next major release My config: ```auto # Enables you to specify a file where Kibana stores log output. #logging.dest: stdout #DEPRECATED #logging.dest: /var/data/log/kibana/kibana.log # Set the value of this setting to true to suppress all logging output. #logging.silent: false # Set the value of this setting to true to suppress all logging output other than error messages. #logging.quiet: false # Set the value of this setting to true to log all events, including system usage information # and all requests. #logging.verbose: false #logging.verbose: true logging: appenders: file: type: file fileName: /var/data/log/kibana/kibana.log layout: type: pattern root: appenders: [default,file] ``` Documentation mentions the properties: > **[Configure Kibana | Kibana Guide \[7.16\] | Elastic](https://www.elastic.co/guide/en/kibana/7.16/settings.html)** > > A reference of the reporting settings administrators configure in kibana.yml. ---
**Author:** ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)\ **Post date:** [January 13, 2022, 10:02pm UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/7 "2022-01-13T22:02:07Z")
If you are using the debian/rpm packages you can ignore this deprecation warning. Starting in 7.17 this deprecation warning will no longer show on these platforms [[7.17] [deb/rpm] Skip deprecation warning for logging.dest by jbudz · Pull Request #120273 · elastic/kibana · GitHub](https://github.com/elastic/kibana/pull/120273) When upgrading to 8.0 Kibana the new package will correctly configure the new logging format, so no action is required. ---
**Author:** ![KillianS](https://avatars.discourse-cdn.com/v4/letter/k/f6c823/32.png) [@KillianS](https://discuss.elastic.co/u/KillianS)\ **Post date:** [January 18, 2022, 10:03am UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/8 "2022-01-18T10:03:16Z")
Hi, I tried this and that's not working. I also upgrade to 7.16.3 and problem is still here. ---
**Author:** ![KillianS](https://avatars.discourse-cdn.com/v4/letter/k/f6c823/32.png) [@KillianS](https://discuss.elastic.co/u/KillianS)\ **Post date:** [January 18, 2022, 10:09am UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/9 "2022-01-18T10:09:02Z")
Hi, Okay I'm waiting for the 7.17 to be release to see if this solve the issu. ---
**Author:** ![KillianS](https://avatars.discourse-cdn.com/v4/letter/k/f6c823/32.png) [@KillianS](https://discuss.elastic.co/u/KillianS)\ **Post date:** [February 2, 2022, 8:17am UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/10 "2022-02-02T08:17:42Z")
Hi, Upgrading to 7.17 fix the issue. ---
**Author:** ![VamPikmin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vampikmin/32/22367_2.png) [@VamPikmin](https://discuss.elastic.co/u/VamPikmin)\ **Post date:** [February 12, 2022, 2:57am UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/11 "2022-02-12T02:57:58Z")
Upgrading to 7.17.0 didn't fix the issue for me Upgrading to 8.0.0 didn't fix the issue I had to backup my config and apt purge kibana Once I reinstalled and put back the config it was fine (the kibana unit file still had the --logging.dest set) ---
**Author:** ![C0rn3j](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/c0rn3j/32/102095_2.png) [@C0rn3j](https://discuss.elastic.co/u/C0rn3j)\ **Post date:** [February 21, 2022, 7:27pm UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/12 "2022-02-21T19:27:34Z")
Looks like that was probably caused by Kibana 7 having its service in `/etc/systemd/system/kibana.service` but Kibana 8 has it in `/usr/lib/systemd/system/kibana.service` and it does not look like upgrading deletes the old one, so both end up being there and the one in /etc has the priority. I had to do the following to get Kibana back up and running: ```nohighlight mv /etc/systemd/system/kibana.service /etc/systemd/system/kibana.service.disabled systemctl daemon-reload && systemctl restart kibana ``` ---
**Author:** ![KillianS](https://avatars.discourse-cdn.com/v4/letter/k/f6c823/32.png) [@KillianS](https://discuss.elastic.co/u/KillianS)\ **Post date:** [March 3, 2022, 10:07am UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/13 "2022-03-03T10:07:25Z")
Yes, in 7.17 the warning message disapear but when upgrading to 8.0 i could not restart Kibana, I did the same step like you and that's fix the problem. It seems ELK Team just remove the warning message but didn't fix the issue for the upgrade. ---
**Author:** ![VamPikmin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vampikmin/32/22367_2.png) [@VamPikmin](https://discuss.elastic.co/u/VamPikmin)\ **Post date:** [March 4, 2022, 10:19am UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/14 "2022-03-04T10:19:48Z")
Glad it worked. @C0rn3j I tried to disable the service but I don't think it was enough. ```auto systemctl disable kibana ``` I have another server to upgrade so I'll try it one more time just to be sure. So many changes lately, it's hard to keep track, ECS, composable index templates, fleet ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 1, 2022, 10:20am UTC](https://discuss.elastic.co/t/kibana-setting-logging-dest-is-deprecated-cant-be-fixed/291424/15 "2022-04-01T10:20:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.