You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to include source metadata as a unique identifier for every file handled in CLI when collecting metrics for the commands executed.
How will this change help?
This change will allow us to measure the Time to first API Design metric as described here.
How could it be implemented/designed?
We need to consider two different issues we've found so far:
The hashing algorithm to use: We should make a decision based on computational cost and security aspects according to New Relic requirements and also the recommendations from SonarCloud. Some research about algorithms like md5, sha1 or sha256 is needed.
Find another way to calculate the Time to first API Design metric, or a different way to identify the source so it doesn't change between file creation and generation. See feat: add POC for measuring adoption #859 (comment)
I have opened a PR that addresses this issue. it will collect the birth timestamp of the file that cli works on. IMO it solves the issue provides the best value and more insight into the file.
Why do we need this improvement?
We need to include
source
metadata as a unique identifier for every file handled in CLI when collecting metrics for the commands executed.How will this change help?
This change will allow us to measure the
Time to first API Design
metric as described here.How could it be implemented/designed?
We need to consider two different issues we've found so far:
md5
,sha1
orsha256
is needed.Time to first API Design
metric, or a different way to identify the source so it doesn't change between file creation and generation. See feat: add POC for measuring adoption #859 (comment)Related issue(s)
Relates to #1161
The text was updated successfully, but these errors were encountered: