# Mute deprecation warns

**URL:** https://forum.opensearch.org/t/mute-deprecation-warns/7942
**Category:** OpenDistro
**Tags:** troubleshoot
**Created:** [December 10, 2021, 9:14am UTC](https://forum.opensearch.org/t/mute-deprecation-warns/7942 "2021-12-10T09:14:45Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![stdmje](https://avatars.discourse-cdn.com/v4/letter/s/f17d59/32.png) [@stdmje](https://forum.opensearch.org/u/stdmje)
#### Post date: [December 10, 2021, 9:14am UTC](https://forum.opensearch.org/t/mute-deprecation-warns/7942/1 "2021-12-10T09:14:45Z")

</div>

Hello,

I am trying to mute DEPRECATION warning in the logs but doing it via \_cluster/settings is not working.

Log to mute

```auto
[2021-12-10T09:14:32,563][DEPRECATION][o.o.d.c.m.IndexNameExpressionResolver] [opensearch-replica-master-1] this request accesses system indices: [.opendistro_security, .tasks], but in a future major version, direct access to system indices will be prevented by default

```

```auto
PUT /_cluster/settings
{
  "persistent" : {
    "logger.deprecation.level" : "ERROR"
  }
}

```

I followed the docs [Logs - OpenSearch documentation](https://opensearch.org/docs/latest/opensearch/logs/#deprecation-logs)

Any advice?

Thanks in advance

---

<div class="post-metadata">

### Author: ![stdmje](https://avatars.discourse-cdn.com/v4/letter/s/f17d59/32.png) [@stdmje](https://forum.opensearch.org/u/stdmje)
#### Post date: [February 2, 2022, 7:35am UTC](https://forum.opensearch.org/t/mute-deprecation-warns/7942/2 "2022-02-02T07:35:17Z")

</div>

Still waiting for a fix in 1.2.3

Anybody?

---

<div class="post-metadata">

### Author: ![jbolle](https://avatars.discourse-cdn.com/v4/letter/j/65b543/32.png) [@jbolle](https://forum.opensearch.org/u/jbolle)
#### Post date: [February 2, 2022, 5:52pm UTC](https://forum.opensearch.org/t/mute-deprecation-warns/7942/3 "2022-02-02T17:52:55Z")

</div>

When on ElasticSearch I had a huge number of log lines firing that were not useful. While not deprecation specific, you might try this:

```auto
PUT _cluster/settings?flat_settings=true&pretty
{
    "transient" : {
        "logger.com.full.java.package.class": "ERROR"
    }
}

```

You have to put in the full Java pacakge and class path, and what you showed is just the shortened version. From quickly searching the source, it looks like the full path should be something like:  
org.opensearch.cluster.metadata.IndexNameExpressionResolver , however there is an extra `d` in the shortening. Maybe `deprecation`?

---

<div class="post-metadata">

### Author: ![stdmje](https://avatars.discourse-cdn.com/v4/letter/s/f17d59/32.png) [@stdmje](https://forum.opensearch.org/u/stdmje)
#### Post date: [February 3, 2022, 7:46am UTC](https://forum.opensearch.org/t/mute-deprecation-warns/7942/4 "2022-02-03T07:46:59Z")

</div>

Thanks @jbolle

I tried with _logger.com.full.java.package.class_ with no luck. Still getting those useless deprecation messages.

---

<div class="post-metadata">

### Author: ![jbolle](https://avatars.discourse-cdn.com/v4/letter/j/65b543/32.png) [@jbolle](https://forum.opensearch.org/u/jbolle)
#### Post date: [February 4, 2022, 2:54am UTC](https://forum.opensearch.org/t/mute-deprecation-warns/7942/5 "2022-02-04T02:54:39Z")

</div>

> [@stdmje](#):
>
> I tried with _logger.com.full.java.package.class_ with no luck. Still getting those useless deprecation messages.

If that is what you put in the rest command then I wouldn’t expect it to work. You need to put the full class name of the logger. However its difficult to exactly determine what that class name is because the logger is using the dot shortening.