-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(metrics): [NAN-664] track more usage metrics in datadog #2136
feat(metrics): [NAN-664] track more usage metrics in datadog #2136
Conversation
@@ -1,41 +1,45 @@ | |||
import tracer from 'dd-trace'; | |||
|
|||
export enum Types { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
alphabetize
|
||
const action = LogActionEnum.TOKEN; | ||
|
||
if (!isSync) { | ||
metrics.increment(metrics.Types.GET_CONNECTION, 1, { accountId }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does that create a metric per account? If yes are we ok about the cost increase? cc @bastienbeurier
Same question about the other ones below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The description of the task states:
Because we pay per number of metrics, we should track 0-1 dimensions for each metric. I would only track accountID.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, same comment as @TBonnin
Describe your changes
Add additional metric tracking
Issue ticket number and link
NAN-664
Checklist before requesting a review (skip if just adding/editing APIs & templates)