# Elasticsearch X-Opaque-Id Not in application.log Exception
**URL:** https://discuss.elastic.co/t/elasticsearch-x-opaque-id-not-in-application-log-exception/216739
**Category:** Elasticsearch
**Created:** [January 27, 2020, 11:53pm UTC](https://discuss.elastic.co/t/elasticsearch-x-opaque-id-not-in-application-log-exception/216739 "2020-01-27T23:53:10Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@y\_xi](https://discuss.elastic.co/u/y_xi)
#### Post date: [January 27, 2020, 11:53pm UTC](https://discuss.elastic.co/t/elasticsearch-x-opaque-id-not-in-application-log-exception/216739/1 "2020-01-27T23:53:10Z")
In [https://github.com/elastic/elasticsearch/issues/31521](https://github.com/elastic/elasticsearch/issues/31521) Elasticsearch added [X-Opaque-Id](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/tasks.html) to slow log and access log. One more use case for me is to link X-Opaque-Id to exception trace whenever ES throws exception, which would be logged in root level ES application.log
I'm wondering if there is any support plan or workaround to achieve it, that I would be able to link TaskId to ES exception trace in the log? Meanwhile I created Issue [https://github.com/elastic/elasticsearch/issues/51451](https://github.com/elastic/elasticsearch/issues/51451) in the backlog
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 24, 2020, 11:53pm UTC](https://discuss.elastic.co/t/elasticsearch-x-opaque-id-not-in-application-log-exception/216739/2 "2020-02-24T23:53:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.