# Deprecation Log Spam

**URL:** <https://discuss.elastic.co/t/deprecation-log-spam/332851>\
**Category:** Elasticsearch\
**Created:** [May 9, 2023, 2:01am UTC](https://discuss.elastic.co/t/deprecation-log-spam/332851 "2023-05-09T02:01:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)\
**Post date:** [May 9, 2023, 2:01am UTC](https://discuss.elastic.co/t/deprecation-log-spam/332851/1 "2023-05-09T02:01:26Z")

</div>

The below line is blowing up my log files. What is it and what do I need to do to get it to stop?

```auto
[2023-05-03T22:10:15,259][WARN][o.e.d.c.m.IndexNameExpressionResolver] [elastic.contoso.net] data_stream.dataset="deprecation.elasticsearch" data_stream.namespace="default" data_stream.type="logs" elasticsearch.event.category="api" event.code="open_system_index_access" message="this request accesses system indices: [.apm-agent-configuration, .apm-custom-link, .async-search, .fleet-actions-7, .fleet-agents-7, .fleet-enrollment-api-keys-7, .fleet-policies-7, .fleet-policies-leader-7, .fleet-servers-7, .kibana_1, .kibana_10, .kibana_11, .kibana_2, .kibana_3, .kibana_4, .kibana_5, .kibana_6, .kibana_7, .kibana_7.12.0_001, .kibana_7.13.0_001, .kibana_7.13.3_001, .kibana_7.16.1_001, .kibana_8, .kibana_8.0.0_001, .kibana_8.2.2_001, .kibana_8.4.3_001, .kibana_9, .kibana_security_session_1, .kibana_task_manager_1, .kibana_task_manager_2, .kibana_task_manager_3, .kibana_task_manager_4, .kibana_task_manager_5, .kibana_task_manager_6, .kibana_task_manager_7.12.0_001, .kibana_task_manager_7.13.0_001, .kibana_task_manager_7.13.3_001, .kibana_task_manager_7.16.1_001, .kibana_task_manager_8.0.0_001, .kibana_task_manager_8.2.2_001, .kibana_task_manager_8.4.3_001, .ml-config, .reporting-2019.06.09, .reporting-2020-09-06, .reporting-2022-05-08, .reporting-2022-06-05, .reporting-2022-07-24, .reporting-2022-08-14, .reporting-2022-08-28, .reporting-2022-09-04, .reporting-2022-09-25, .reporting-2022-10-23, .reporting-2022-10-30, .reporting-2022-11-27, .reporting-2022-12-25, .reporting-2023-01-29, .reporting-2023-02-12, .reporting-2023-02-26, .reporting-2023-03-05, .reporting-2023-03-12, .reporting-2023-03-19, .reporting-2023-03-26, .reporting-2023-04-09, .reporting-2023-04-16, .reporting-2023-04-23, .reporting-2023-04-30, .security-7, .security-profile-8, .tasks, .transform-internal-005, .transform-internal-006, .transform-internal-007, .triggered_watches, .watches], but in a future major version, direct access to system indices will be prevented by default"

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 11, 2023, 3:09am UTC](https://discuss.elastic.co/t/deprecation-log-spam/332851/2 "2023-05-11T03:09:17Z")

</div>

Are you using Kibana?

---

<div class="post-metadata">

**Author:** ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)\
**Post date:** [May 11, 2023, 3:43pm UTC](https://discuss.elastic.co/t/deprecation-log-spam/332851/3 "2023-05-11T15:43:02Z")

</div>

> [@warkolm](#):
>
> Are you using Kibana?

Yes sir.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 8, 2023, 3:43pm UTC](https://discuss.elastic.co/t/deprecation-log-spam/332851/4 "2023-06-08T15:43:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.