tjiuming commented on issue #18243:
URL: https://github.com/apache/pulsar/issues/18243#issuecomment-1296981244
> > How are metadata store metrics used currently? I think it could be a
breaking change if CommandPartitionedTopicMetadata requests are tracked as part
of some other metric. I think it should be a new metric that is unique for
CommandPartitionedTopicMetadata requests. @codelipenghui do you have a
suggestion?
>
> The metadata store metrics are on the metadata store level which can
provide the metastore operation latency. The REST API request metrics should be
a separate part. The CommandPartitionedTopicMetadata requests metrics should
not 100% equal to the metadata store operation. Maybe the jetty thread is
blocked somewhere.
>
> I think maybe jetty already provides the ability to expose the metrics
with the request path label?
I've checked jetty, seems there are no such ability.
if we want the ability, it's not easy. because we need to converge the
request path. such as: `/api/v2/persistent/myTenant/myNamespace/partitioned` ->
`/api/v2/persistent/{tenant}/{namespace}/partitioned`. it may takes some time
--
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]
