[SCB-6] ServiceComb Java Chassis Metrics

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: java-chassis-1.0.0-m2
• Component/s: Java-Chassis
• Assignee: Yangyong Zheng
• Reporter: Yangyong Zheng
• Created: 19/Dec/17 10:37
• Updated: 20/Apr/18 02:33
• Resolved: 20/Apr/18 02:33

Description

As a microservice framework,servicecomb java chassis need support user collect metrics such as tps,latency and system resource usage etc,then use this collected data making some policy like scaling strategy further.

The relation between Java Chassis and Java Chassis Metrics is similar to Spring boot and Spring boot actuator.

Issue Links

• links to: GitHub Pull Request #580

Sub-Tasks

• EventBus in Java Chassis: Resolved
• Metrics core module: Resolved
• Implement CallCount and TPS Metrics: Resolved
• Implement Runtime System Resources Usage Metrics: Resolved
• Metrics Auto Publish: Resolved
• Support Custom Metrics: Resolved
• Upgrade Metrics File Output from 0.5.0 to 1.0.0-m1: Resolved
• All Monitor can convert to Map with plain-key when polling data: Resolved
• Metrics need support prometheus Integration: Resolved
• Add Consumer side event trigger for collect metrics data: Resolved
• User Guide and Quick Start for Metrics 1.0.0-m1: Resolved
• Add Success / Fail Dimension for Invocation: Resolved
• Support HealthCheck: Resolved
• Metrics support overwatch Integration: Closed
• Support Record Custom Metrics in Java Chassis Itself: Closed
• Remove custom metrics implementation: Resolved
• Using the EventManager directly without creating another wrapper: Closed
• Update metrics publish data module: Resolved
• Fix metrics write file samples add status code to file name: Resolved
• Fix Bug for register custom monitor without any tags: Resolved
• Metrics timer (like latency) output precision must to nano level not milli level: Closed
• support user set prometheus exporter address not only port: Resolved