How to stop elasticsearch warnings (Deprecated field [from] used, this field is unused and will be removed entirely) in camunda.log

Camunda 8 Topics Discussion & Questions
1

I am using c8run 8.8 alpha8
and I see hunderds of warnings for elasticsearch as follows:

org.elasticsearch.client.RestClient -
request [POST ``http://localhost:9200/operate-operation-8.4.1_/_search?typed_keys=true&max_concurrent_shard_requests=5&search_type=query_then_fetch&batched_reduce_size=512``]
returned 4 warnings: [299 Elasticsearch-8.17.3-a091390de485bd4b127884f7e565c0cad59b10d2
“Deprecated field [from] used, this field is unused and will be removed entirely”],
[299 Elasticsearch-8.17.3-a091390de485bd4b127884f7e565c0cad59b10d2
“Deprecated field [to] used,
this field is unused and will be removed entirely”],[299 Elasticsearch-8.17.3-a091390de485bd4b127884f7e565c0cad59b10d2
“Deprecated field [include_lower] used,
this field is unused and will be removed entirely”],
[299 Elasticsearch-8.17.3-a091390de485bd4b127884f7e565c0cad59b10d2
“Deprecated field [include_upper] used, this field is unused and will be removed entirely”]

Please advise how to stop those warnings because it is filling my log file.

2

Hi @devmsaleh,

The Elasticsearch warnings you’re seeing in your Camunda 8.8 alpha8 logs are related to deprecated fields in Elasticsearch 8.x. These warnings occur because Camunda is using queries that contain fields like from, to, include_lower, and include_upper which are now deprecated and unused in newer Elasticsearch versions.

Quick Solution: Disable Deprecation Logging

Since you’re using Elasticsearch 8.16.0 or higher, the recommended approach is to turn off deprecation logging to reduce the log noise. You can do this with the following command:

curl -X PUT "http://localhost:9200/_cluster/settings" \
  -H "Content-Type: application/json" \
  -d '{
    "persistent": {
      "logger.org.elasticsearch.deprecation": "OFF"
    }
  }'

This will suppress the deprecation warnings in your logs immediately.

Important Notes

  • Functionality: These warnings don’t break any functionality - they’re just informational about deprecated fields
  • Future compatibility: While suppressing the warnings solves the immediate log noise issue, the underlying queries should eventually be updated for future Elasticsearch compatibility
  • Default setup: If you’re using the default Camunda setup (which it sounds like you are with c8run), these warnings are generally safe to ignore for now

Alternative Approaches

If you prefer not to disable deprecation logging globally, you can also:

  • Wait for future Camunda updates that will address these deprecated field usages
  • Monitor for any custom index templates or queries you might have that use these fields

The warnings are a known issue with Elasticsearch 8.x compatibility and don’t indicate any problems with your Camunda installation.

References:

Let me know if you need any clarification or if the curl command resolves the log noise issue!