Elasticsearch Version
9.x
Installed Plugins
No response
Java Version
bundled
OS Version
n/a
Problem Description
When retrieving a shutdown status, we include information like:
{
"node_id": "a8qEx_uNRlCR2Gj-h_ZNGQ",
"node_ephemeral_id": "hXIHGbc3Tlig0su-bx1FTw",
"type": "SIGTERM",
"reason": "node sigterm",
"shutdown_startedmillis": 1765757170089,
"status": "COMPLETE",
"shard_migration": {
"status": "COMPLETE",
…
Which includes the "shutdown_startedmillis" field. Almost all of our time-based fields in ES use _millis as the non-human readable field name. It would be great if this could follow the same pattern and be called "shutdown_started_millis" instead.
Steps to Reproduce
Retrieve any shutdown status.
Logs (if relevant)
No response
Elasticsearch Version
9.x
Installed Plugins
No response
Java Version
bundled
OS Version
n/a
Problem Description
When retrieving a shutdown status, we include information like:
{ "node_id": "a8qEx_uNRlCR2Gj-h_ZNGQ", "node_ephemeral_id": "hXIHGbc3Tlig0su-bx1FTw", "type": "SIGTERM", "reason": "node sigterm", "shutdown_startedmillis": 1765757170089, "status": "COMPLETE", "shard_migration": { "status": "COMPLETE", …Which includes the
"shutdown_startedmillis"field. Almost all of our time-based fields in ES use_millisas the non-human readable field name. It would be great if this could follow the same pattern and be called"shutdown_started_millis"instead.Steps to Reproduce
Retrieve any shutdown status.
Logs (if relevant)
No response