we want to know invocations of success/failed or different transport, their composition of time usage, average time of fiters/handlers/queue in threadPool/business executin, and so on not for when a invocation in queue, if it is success or failed.
2018-01-11 9:03 GMT+08:00 郑扬勇 <[email protected]>: > Sorry,seems table format missing: > > Group Level Catalog Metrics Success/Failed Rest/Highway > servicecomb instance/<operationName> producer waitInQueue count × × > servicecomb instance/<operationName> producer lifeTimeInQueue average × × > servicecomb instance/<operationName> producer lifeTimeInQueue max × × > servicecomb instance/<operationName> producer lifeTimeInQueue min × × > servicecomb instance/<operationName> producer executionTime average √ × > servicecomb instance/<operationName> producer executionTime max √ × > servicecomb instance/<operationName> producer executionTime min √ × > servicecomb instance/<operationName> producer producerLatency average √ √ > servicecomb instance/<operationName> producer producerLatency max √ √ > servicecomb instance/<operationName> producer producerLatency min √ √ > servicecomb instance/<operationName> producer producerCall total √ × > servicecomb instance/<operationName> producer producerCall tps √ × > servicecomb instance/<operationName> consumer consumerLatency average √ √ > servicecomb instance/<operationName> consumer consumerLatency max √ √ > servicecomb instance/<operationName> consumer consumerLatency min √ √ > servicecomb instance/<operationName> consumer consumerCall total √ × > servicecomb instance/<operationName> consumer consumerCall tps √ × > ------------------ 原始邮件 ------------------ > 发件人: "郑扬勇";<[email protected]>; > 发送时间: 2018年1月11日(星期四) 上午8:59 > 收件人: "dev"<[email protected]>; > > 主题: [Discussion]Add two Success/Failed and Rest/Highway Dimensions for > Metrics > > > > Hi,everyone: > It's well known that this two Dimensions may very useful when tracking > call problem,here is my design: > Group Level Catalog Metrics Success/Failed Rest/Highway > servicecomb instance system cpu load > servicecomb instance system cpu runningThreads > servicecomb instance system heap init > servicecomb instance system heap max > servicecomb instance system heap commit > servicecomb instance system heap used > servicecomb instance system nonHeap init > servicecomb instance system nonHeap max > servicecomb instance system nonHeap commit > servicecomb instance system nonHeap used > servicecomb instance/<operationName> producer waitInQueue count > servicecomb instance/<operationName> producer lifeTimeInQueue average > servicecomb instance/<operationName> producer lifeTimeInQueue max > servicecomb instance/<operationName> producer lifeTimeInQueue min > servicecomb instance/<operationName> producer executionTime average √ > servicecomb instance/<operationName> producer executionTime max √ > servicecomb instance/<operationName> producer executionTime min √ > servicecomb instance/<operationName> producer producerLatency average √ √ > servicecomb instance/<operationName> producer producerLatency max √ √ > servicecomb instance/<operationName> producer producerLatency min √ √ > servicecomb instance/<operationName> producer producerCall total √ > servicecomb instance/<operationName> producer producerCall tps √ > servicecomb instance/<operationName> consumer consumerLatency average √ √ > servicecomb instance/<operationName> consumer consumerLatency max √ √ > servicecomb instance/<operationName> consumer consumerLatency min √ √ > servicecomb instance/<operationName> consumer consumerCall total √ > servicecomb instance/<operationName> consumer consumerCall tps √ > > If there is a √ means will add this dimension support. > Thanks for check if any is missing,or any suggestion is welcome! > > Best Regards & Thanks! > zhengyangyong >
