# Enabling Trace Logging for a shard/index

**URL:** <https://discuss.elastic.co/t/enabling-trace-logging-for-a-shard-index/376486>\
**Category:** Elasticsearch\
**Created:** [March 27, 2025, 2:45pm UTC](https://discuss.elastic.co/t/enabling-trace-logging-for-a-shard-index/376486 "2025-03-27T14:45:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aditya\_Teltia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aditya_teltia/32/122447_2.png) [@Aditya\_Teltia](https://discuss.elastic.co/u/Aditya_Teltia)\
**Post date:** [March 27, 2025, 2:45pm UTC](https://discuss.elastic.co/t/enabling-trace-logging-for-a-shard-index/376486/1 "2025-03-27T14:45:51Z")

</div>

Hi Team,

Is there a way to enable trace logging for a particular shard or particular index in elasticsearch.

I tried doing this but it didn't work

```auto
PUT _cluster/settings
{
  "transient": {
    "logger.org.elasticsearch.index.engine.Engine.index_name.3": "TRACE"
  }
}

```

3 is shardId in above.

---

<div class="post-metadata">

**Author:** ![Aditya\_Teltia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aditya_teltia/32/122447_2.png) [@Aditya\_Teltia](https://discuss.elastic.co/u/Aditya_Teltia)\
**Post date:** [March 28, 2025, 4:50am UTC](https://discuss.elastic.co/t/enabling-trace-logging-for-a-shard-index/376486/2 "2025-03-28T04:50:30Z")

</div>

Can someone please confirm if this is possible?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 28, 2025, 5:07am UTC](https://discuss.elastic.co/t/enabling-trace-logging-for-a-shard-index/376486/3 "2025-03-28T05:07:42Z")

</div>

As far as I know that is not possible. What is the problem you are trying to solve?

---

<div class="post-metadata">

**Author:** ![Aditya\_Teltia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aditya_teltia/32/122447_2.png) [@Aditya\_Teltia](https://discuss.elastic.co/u/Aditya_Teltia)\
**Post date:** [March 28, 2025, 5:24am UTC](https://discuss.elastic.co/t/enabling-trace-logging-for-a-shard-index/376486/4 "2025-03-28T05:24:56Z")

</div>

I have one shard failing during commit with NoSuchFileException frequently and then it comes back green again. I want to enable trace logging for that shard to understand what is the issue exactly.

Enabling TRACE logging for class Engine isn't recommended afaik

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 28, 2025, 5:28am UTC](https://discuss.elastic.co/t/enabling-trace-logging-for-a-shard-index/376486/5 "2025-03-28T05:28:13Z")

</div>

It would probably help if you provided some additional details.

- Which version of Elasticsearch are you using?
- What is the size and specification of your cluster?
- What type of storage are you using?

It would probably also help if you shared the full error message, possibly with some lines around it for context.