Skip to end of metadata
Go to start of metadata

Background

  • Common library used by all clients that want to report to StatisticsService.

Simplify the implementation in each module.

Usage responsibility

  • Collect data specified in StatisticsService
  • Non-blocking behavior
  • Low latency
  • Low on network activity.
    • Avoid "fan-out" effect. A single request must have not more than one additional network function used for statistics.

Performance and HealthCheck responsibility.

Recomend to reuse Dropwizard Metrics for health check and performance reporting.
See Metrics Spring for @Timed, @Gauge etc.
We then need to create our own Reporter, based on Metrics-Graphite

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.