ektravel commented on code in PR #13815:
URL: https://github.com/apache/druid/pull/13815#discussion_r1110076652


##########
docs/operations/metrics.md:
##########
@@ -221,7 +221,7 @@ batch ingestion emit the following metrics. These metrics 
are deltas for each em
 |`ingest/merge/cpu`|Cpu time in Nanoseconds spent on merging intermediate 
segments.|`dataSource`, `taskId`, `taskType`, `tags`|Depends on configuration. 
Generally a few minutes at most.|
 |`ingest/handoff/count`|Number of handoffs that happened.|`dataSource`, 
`taskId`, `taskType`, `tags`|Varies. Generally greater than 0 once every 
segment granular period if cluster operating normally.|
 |`ingest/sink/count`|Number of sinks not handoffed.|`dataSource`, `taskId`, 
`taskType`, `tags`|1~3|
-|`ingest/events/messageGap`|Time gap in milliseconds between the latest 
ingested event timestamp and the current system timestamp of metrics emission. 
|`dataSource`, `taskId`, `taskType`, `tags`|Greater than 0, depends on the time 
carried in event. |
+|`ingest/events/messageGap`|Time gap in milliseconds between the latest 
ingested event timestamp and the current system timestamp of metrics emission. 
If this is increasing but lag is low, it likely means that druid is not getting 
new data. This metric will get reset as new tasks spawn up.|`dataSource`, 
`taskId`, `taskType`, `tags`|Greater than 0, depends on the time carried in 
event. |

Review Comment:
   ```suggestion
   |`ingest/events/messageGap`|Time gap in milliseconds between the latest 
ingested event timestamp and the current system timestamp of metrics emission. 
If the value is increasing but lag is low, Druid may not be receiving new data. 
This metric gets reset as new tasks spawn up.|`dataSource`, `taskId`, 
`taskType`, `tags`|Greater than 0, depends on the time carried in event. |
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to