Stack monitoring not showing replica index rate

After upgrading to 8.18.1 the stack monitoring in Kibana is not showing the index rate for replica shards.

This behavior exists even after upgrading to 8.19.2.

Checking the statistics through the _stats API call shows that the indexing rate for ‘total’ and ‘primaries’ is different which would suggest that the data is being retrieved properly.

"primaries": {
      "indexing": {
        "index_total": 269009253,
        "index_time_in_millis": 23063033,
        "index_current": 1,
        "index_failed": 15814841,
        "index_failed_due_to_version_conflict": 15814841,
        "delete_total": 414623,
        "delete_time_in_millis": 6141,
        "delete_current": 0,
        "noop_update_total": 0,
        "is_throttled": false,
        "throttle_time_in_millis": 0,
        "write_load": 0.0004900165176633547
      }
    "total": {
      "indexing": {
        "index_total": 536570546,
        "index_time_in_millis": 44488414,
        "index_current": 1,
        "index_failed": 15814841,
        "index_failed_due_to_version_conflict": 15814841,
        "delete_total": 639814,
        "delete_time_in_millis": 9507,
        "delete_current": 0,
        "noop_update_total": 0,
        "is_throttled": false,
        "throttle_time_in_millis": 0,
        "write_load": 0.0006280360207538013
      }

When looking at the indexing rate for individual indices the graph displays properly:

I don’t see anything in the release notes regarding this as either a change or a known issue. This was displaying properly in 8.18.0. I don’t see any errors in the Kibana log relating to this.

Did I miss something about this in the release notes?

Hello @twilson

As per documentation do not see any changes to this graph :

Checked using GET /_stats , can see similar output as yours :

Primaries :
"indexing": {
        "index_total": 48336,
        "index_time_in_millis": 18456
		}
	  
Total :
"indexing": {
        "index_total": 77037,
        "index_time_in_millis": 27754
     }	

So it seems to be a bug :thinking:

Thanks!!

1 Like