Add Indexing Latency, Indexing and Search Rate metric per shard#797
Add Indexing Latency, Indexing and Search Rate metric per shard#797arpitpatawat wants to merge 4 commits intoopensearch-project:mainfrom
Conversation
Signed-off-by: Arpit Patawat <arpitptw@amazon.com>
arpitpatawat
requested review from
Gaganjuneja,
Shephalimittal,
ansjcy,
khushbr,
nishchay21,
psychbot,
rramachand21 and
sbcd90
as code owners
| initializeMetricsIfNeeded(); | ||
| LOG.debug("Executing collect metrics for RTFShardOperationRateCollector"); | ||
|
|
||
| long currentTimeInMillis = System.currentTimeMillis(); |
There was a problem hiding this comment.
What will be value in this scenario - 100 request came on a shard and 10:01:00 and another 100 (so in total 200) at 10:05:00. Last collection happened at 10:04:55 and now its happening at 10:05:00. So minutesSinceLastCollection would be (5000/60000 = .083) and the rate would be (200 - 100)/0.083 = 1204.81. Is this the right calculation or am missing something?
There was a problem hiding this comment.
Will change the rate to 5 second and remove the difference between the last collection time to make sure it will only publish the current diff, despite the time difference with last collection.
| "Indexing operations per minute per shard", | ||
| MetricUnits.RATE.toString()); | ||
|
|
||
| searchRateHistogram = |
There was a problem hiding this comment.
Rename as this is not histo
.../org/opensearch/performanceanalyzer/collectors/telemetry/RTFShardOperationRateCollector.java
Show resolved
Hide resolved
| indexingRateHistogram.add(indexingRatePerMinute, tags); | ||
| } | ||
|
|
||
| private void processSearchOperations( |
There was a problem hiding this comment.
Can you add a sample metrics for this as to how the dimensions are looking like
Signed-off-by: Arpit Patawat <arpitptw@amazon.com>
Signed-off-by: Arpit Patawat <arpitptw@amazon.com>
|
|
||
| fetchPhaseHistogram.record( | ||
| fetchTimeInMills, createTags(searchContext, SHARD_FETCH_PHASE, false)); | ||
| queryPlusFetchPhaseHistogram.record( |
There was a problem hiding this comment.
Should we add the phase here? It defeats the purpose of this metric.
There was a problem hiding this comment.
Updated the metric tags to have same value for phase, so that both metrics are the same.
Signed-off-by: Arpit Patawat <arpitptw@amazon.com>
| LogManager.getLogger(RTFPerformanceAnalyzerSearchListener.class); | ||
| private static final String SHARD_FETCH_PHASE = "shard_fetch"; | ||
| private static final String SHARD_QUERY_PHASE = "shard_query"; | ||
| private static final String SHARD_QUERY_PLUS_FETCH_PHASE = "shard_query_plus_fetch"; |
There was a problem hiding this comment.
Should we just call search.latency ?
| @@ -38,6 +39,7 @@ public class RTFPerformanceAnalyzerSearchListener | |||
| LogManager.getLogger(RTFPerformanceAnalyzerSearchListener.class); | |||
| private static final String SHARD_FETCH_PHASE = "shard_fetch"; | |||
There was a problem hiding this comment.
Please change to Otel standards shard.fetch this is same for all dimensions added
3 participants
Description
This commit will add 3 metrics per shard which are -
These will be helpful to get detailed insights at shard level.
Related Issues
None
Check List
--signoff.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.