# CRITICAL Deprecation log while Upgrading Elasticsearch from v8.4.1 to v8.11.2
**URL:** https://discuss.elastic.co/t/critical-deprecation-log-while-upgrading-elasticsearch-from-v8-4-1-to-v8-11-2/356945
**Category:** Elasticsearch
**Tags:** elastic-stack-monitoring, elastic-stack-security, elastic-stack-alerting
**Created:** [April 8, 2024, 6:22am UTC](https://discuss.elastic.co/t/critical-deprecation-log-while-upgrading-elasticsearch-from-v8-4-1-to-v8-11-2/356945 "2024-04-08T06:22:01Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@besanket](https://discuss.elastic.co/u/besanket)
#### Post date: [April 8, 2024, 6:22am UTC](https://discuss.elastic.co/t/critical-deprecation-log-while-upgrading-elasticsearch-from-v8-4-1-to-v8-11-2/356945/1 "2024-04-08T06:22:01Z")
We've observed CRITICAL Deprecation logs while Upgrading Elasticsearch from v8.4.1 to v8.11.2.
Attached below logs for your reference.
```auto
[2024-01-29T15:58:04,984][CRITICAL][o.e.d.r.a.s.RestSearchAction] [dev01]
data_stream.dataset="deprecation.elasticsearch" data_stream.namespace="default"
data_stream.type="logs" elasticsearch.event.category="compatible_api"
event.code="msearch_with_types"
message="[types removal] Specifying types in multi search template requests is deprecated."
```
Few more deprecations warnings observed in the logs as given below.
```auto
[2024-01-25T11:11:32,027][**WARN**][o.e.d.r.RestController ]
[dev01] data_stream.dataset="deprecation.elasticsearch" data_stream.namespace="default"
data_stream.type="logs" elasticsearch.event.category="api"
event.code="deprecated_route_PUT_/_template/{name}"
message="Legacy index templates are deprecated in favor of composable templates."
```
```auto
[2024-01-29T14:25:42,573][**WARN**][o.e.d.i.m.ProvidedIdFieldMapper]
[dev01] data_stream.dataset="deprecation.elasticsearch" data_stream.namespace="default"
data_stream.type="logs" elasticsearch.event.category="aggregations"
event.code="id_field_data"
message="Loading the fielddata on the _id field is deprecated and will be removed in future versions.
If you require sorting or aggregating on this field you should also include the id in the body of your documents,
and map this field as a keyword field that has [doc_values] enabled"
```
```auto
[2024-01-26T13:40:25,841][WARN][o.e.d.c.m.IndexNameExpressionResolver]
[dev01] data_stream.dataset="deprecation.elasticsearch" data_stream.namespace="default"
data_stream.type="logs" elasticsearch.elastic_product_origin="kibana"
elasticsearch.event.category="api"
elasticsearch.http.request.x_opaque_id="6b4def0f-a1db-4bc7-b055-02148d3a2681;kibana:application:management:"
event.code="open_system_index_access"
message="this request accesses system indices: [.async-search, .security-7, .security-profile-8, .security-tokens-7, .tasks, .transform-internal-007],
but in a future major version, direct access to system indices will be prevented by default"
```
Please let us know how this can be fixed?
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [May 3, 2024, 10:35am UTC](https://discuss.elastic.co/t/critical-deprecation-log-while-upgrading-elasticsearch-from-v8-4-1-to-v8-11-2/356945/2 "2024-05-03T10:35:35Z")
> [@besanket](#):
>
> ```auto
> message="[types removal] Specifying types in multi search template requests is deprecated."
>
> ```
You're making multi-search template requests which include types. Stop doing that.
> [@besanket](#):
>
> ```auto
> message="Legacy index templates are deprecated in favor of composable templates."
>
> ```
You're using legacy templates. Use composable templates instead.
> [@besanket](#):
>
> ```auto
> Loading the fielddata on the _id field is deprecated and will be removed in future versions.
> If you require sorting or aggregating on this field you should also include the id in the body of your documents,
> and map this field as a keyword field that has [doc_values] enabled
>
> ```
You're making a request which requires loading the fielddata on the `_id` field. Stop doing that. If you require sorting or aggregating on this field you should also include the id in the body of your documents,
and map this field as a keyword field that has [doc\_values] enabled.
> [@besanket](#):
>
> ```auto
> this request accesses system indices: [.async-search, .security-7, .security-profile-8, .security-tokens-7, .tasks, .transform-internal-007],
> but in a future major version, direct access to system indices will be prevented by default
>
> ```
This one apparently comes from Kibana, should be resolved in a future version.