[GODRIVER-357] Add metrics functionality Created: 10/Apr/18  Updated: 17/Jul/20  Resolved: 17/Jul/20

Status: Closed
Project: Go Driver
Component/s: Monitoring
Affects Version/s: 0.0.2
Fix Version/s: None

Type: Epic Priority: Major - P3
Reporter: Kristofer Brandow (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: FreeMonitoring
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Case:

 Description   

Currently, the only way to extract metrics from the driver is to register for various events (e.g. command events, CMAP events) and calculate statistics in the event handlers.

In addition, there are some statistics exposed by mgo that would not be possible to track even with the current set of events (e.g. total bytes in/out).

This would be very useful for users of the driver for tracking purposes. Finally, if the driver had well designed, consistent statistics in areas, tracking bytes sent and received for purposes of analytics or billing would be vastly easier.

The current requested metrics are:

  • total bytes in/out
    • per downstream, per API
  • commands (per API, per downstream)
  • connections (per downstream)
    • idle
    • total
    • in-use
  • latency distribution
    • per API, downstream
    • ideally with percentiles


 Comments   
Comment by Kristofer Brandow (Inactive) [ 09/May/18 ]

I think it means per downstream server and per API means per collection method.

Comment by Jeffrey Yemin [ 09/May/18 ]

kris.brandow what does "per API, per downstream" mean?

 

Comment by Bernie Hackett [ 10/Apr/18 ]

A lot of this is handled by APM, once the driver has that.

Generated at Thu Feb 08 08:34:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.