Before Creating the Enhancement Request

• I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

Add a new concern standard, dispatchBehindMilliseconds, for the time delay of fast index building tasks relative to the latest news. This new metric will next provide units with more direct time delays, helping users better understand and optimize the real-time nature of the system.

Motivation

While the existing dispatchBehindBytes metric provides information about index build progress, it relies on bytes as a metric, which is not intuitive for understanding actual latency. Especially when the traffic size changes greatly, it is difficult to accurately reflect the true service level only by the number of bytes. The introduction of dispatchBehindMilliseconds can provide a unified and easy-to-understand time unit to evaluate the speed of index construction and help quickly identify potential performance bottlenecks or resource allocation issues.

Describe the Solution You'd Like

Define new attention standards: add dispatchBehindMilliseconds to the existing monitoring system, which is used to represent the time difference between the latest message generation and the successful construction of the current index.

Describe Alternatives You've Considered

Continue using dispatchBehindBytes without making any changes. However, as mentioned earlier, this approach may not fully reflect the actual situation, especially when performance needs to be compared across different environments.
Try to derive the time delay indirectly through other means, such as combining information such as message rate. But doing so is not only complicated, but also difficult to guarantee accuracy.

Additional Context

No response