You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicecomb.apache.org by 郑扬勇 <ya...@qq.com> on 2018/02/03 02:12:43 UTC
[TO ALL]About Metrics publish style
Hello everyone:
Considering we need support user custom metrics better,we must publish metrics data as a more friendly style.
Before we direct publish RegistryMetric model and support convert it into plain key value style like :
servicecomb.instance.system.cpu.load
servicecomb.instance.system.cpu.runningThreads
servicecomb.instance.system.heap.init
servicecomb.instance.system.heap.max
servicecomb.instance/<operationName>.producer.executionTime.average
servicecomb.instance/<operationName>.producer.executionTime.max
servicecomb.instance/<operationName>.producer.executionTime.min
servicecomb.instance/<operationName>.producer.producerCall.total
servicecomb.instance/<operationName>.producer.producerCall.tps
Now we will use same style like spring-cloud-netflix:
jvm(statistic=cpu.load)
jvm(statistic=cpu.runningThreads)
jvm(statistic=heap.init)
jvm(statistic=heap.max)
servicecomb.invocation(statistic=executionTime.average,type=producer,operation=<operationName>,transport=rest,status=200)
servicecomb.invocation(statistic=executionTime.max,type=producer,operation=<operationName>,transport=rest,status=200)
servicecomb.invocation(statistic=executionTime.min,type=producer,operation=<operationName>,transport=rest,status=200)
servicecomb.invocation(statistic=producerCall.total,type=producer,operation=<operationName>,transport=rest,status=200)
servicecomb.invocation(statistic=producerCall.tps,type=producer,operation=<operationName>,transport=rest,status=200)
Best Regards & Thanks
回复： [TO ALL]About Metrics publish style
Posted by 郑扬勇 <ya...@qq.com>.
Hi wjm:
1.OK
2.So we need add a new tag stage like :
servicecomb.invocation(statistic=latency.average,stage=execution,type=producer,operation=<operationName>,transport=rest,status=200)
servicecomb.invocation(statistic=latency.max,stage=execution,type=producer,operation=<operationName>,transport=rest,status=200)
3.will provide later(may in 1.0.0-m2)
4.OK
------------------ 原始邮件 ------------------
发件人: "wjm wjm";<zz...@gmail.com>;
发送时间: 2018年2月3日(星期六) 上午10:35
收件人: "dev"<de...@servicecomb.apache.org>;
主题: Re: [TO ALL]About Metrics publish style
1.min is usless, and spectator already removed min support
2.here statistic mixed statistic and stage, why?
3.we will publish common raw data like spring cloud from maybe by /metrics
4.we will publish our metrics model maybe by /metrics/servicecomb
2018-02-03 10:12 GMT+08:00 郑扬勇 <ya...@qq.com>:
> Hello everyone:
> Considering we need support user custom metrics better,we must publish
> metrics data as a more friendly style.
>
> Before we direct publish RegistryMetric model and support convert it
> into plain key value style like :
> servicecomb.instance.system.cpu.load
> servicecomb.instance.system.cpu.runningThreads
> servicecomb.instance.system.heap.init
> servicecomb.instance.system.heap.max
> servicecomb.instance/<operationName>.producer.executionTime.average
> servicecomb.instance/<operationName>.producer.executionTime.max
> servicecomb.instance/<operationName>.producer.executionTime.min
> servicecomb.instance/<operationName>.producer.producerCall.total
> servicecomb.instance/<operationName>.producer.producerCall.tps
>
> Now we will use same style like spring-cloud-netflix:
> jvm(statistic=cpu.load)
> jvm(statistic=cpu.runningThreads)
> jvm(statistic=heap.init)
> jvm(statistic=heap.max)
>
> servicecomb.invocation(statistic=executionTime.average,type=producer,
> operation=<operationName>,transport=rest,status=200)
> servicecomb.invocation(statistic=executionTime.max,
> type=producer,operation=<operationName>,transport=rest,status=200)
> servicecomb.invocation(statistic=executionTime.min,
> type=producer,operation=<operationName>,transport=rest,status=200)
> servicecomb.invocation(statistic=producerCall.total,
> type=producer,operation=<operationName>,transport=rest,status=200)
> servicecomb.invocation(statistic=producerCall.tps,
> type=producer,operation=<operationName>,transport=rest,status=200)
>
> Best Regards & Thanks
Re: [TO ALL]About Metrics publish style
Posted by wjm wjm <zz...@gmail.com>.
1.min is usless, and spectator already removed min support
2.here statistic mixed statistic and stage, why?
3.we will publish common raw data like spring cloud from maybe by /metrics
4.we will publish our metrics model maybe by /metrics/servicecomb
2018-02-03 10:12 GMT+08:00 郑扬勇 <ya...@qq.com>:
> Hello everyone:
> Considering we need support user custom metrics better,we must publish
> metrics data as a more friendly style.
>
> Before we direct publish RegistryMetric model and support convert it
> into plain key value style like :
> servicecomb.instance.system.cpu.load
> servicecomb.instance.system.cpu.runningThreads
> servicecomb.instance.system.heap.init
> servicecomb.instance.system.heap.max
> servicecomb.instance/<operationName>.producer.executionTime.average
> servicecomb.instance/<operationName>.producer.executionTime.max
> servicecomb.instance/<operationName>.producer.executionTime.min
> servicecomb.instance/<operationName>.producer.producerCall.total
> servicecomb.instance/<operationName>.producer.producerCall.tps
>
> Now we will use same style like spring-cloud-netflix:
> jvm(statistic=cpu.load)
> jvm(statistic=cpu.runningThreads)
> jvm(statistic=heap.init)
> jvm(statistic=heap.max)
>
> servicecomb.invocation(statistic=executionTime.average,type=producer,
> operation=<operationName>,transport=rest,status=200)
> servicecomb.invocation(statistic=executionTime.max,
> type=producer,operation=<operationName>,transport=rest,status=200)
> servicecomb.invocation(statistic=executionTime.min,
> type=producer,operation=<operationName>,transport=rest,status=200)
> servicecomb.invocation(statistic=producerCall.total,
> type=producer,operation=<operationName>,transport=rest,status=200)
> servicecomb.invocation(statistic=producerCall.tps,
> type=producer,operation=<operationName>,transport=rest,status=200)
>
> Best Regards & Thanks