-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore: add telemetry for piece indexer #84
chore: add telemetry for piece indexer #84
Conversation
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.
Need to address #85 first
@NikolasHaimerl can you please resolve merge conflicts and take a stab at unifying naming? |
…/github.com/filecoin-station/deal-observer into nhaimerl-add-telemetry-for-missing-payloads
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.
Almost there 👏
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.
Almost there 👍 Just one name to update and (if I understand correctly) one follow-up issue to create
…/github.com/filecoin-station/deal-observer into nhaimerl-add-telemetry-for-missing-payloads
backend/bin/deal-observer-backend.js
Outdated
recordTelemetry('look_up_payload_cids_stats', point => { | ||
point.intField('total_unresolved_payload_cids', numOfUnresolvedPayloadsCids) | ||
point.intField('payload_cids_resolved', numOfPayloadsCidsResolved) | ||
}) |
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.
Maybe we could simplify all names, include the metric names, WDYT?
recordTelemetry('look_up_payload_cids_stats', point => { | |
point.intField('total_unresolved_payload_cids', numOfUnresolvedPayloadsCids) | |
point.intField('payload_cids_resolved', numOfPayloadsCidsResolved) | |
}) | |
recordTelemetry('look_up_payload_cids_stats', point => { | |
point.intField('unresolved_payload_cids', numOfUnresolvedPayloadsCids) | |
point.intField('resolved_payload_cids, numOfPayloadsCidsResolved) | |
}) |
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.
total_unresolved_payload_cids
refers to the total number all of unresolved payload cids, while resolved_payload_cids
only refers to those resolved in a single round. Putting the unresolved
/resolved
at the beginning of the variable name does make sense though.
Co-authored-by: Julian Gruber <[email protected]>
Co-authored-by: Julian Gruber <[email protected]>
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.
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.
The piece CID indexer fetches the payload CIDs and if it can successfully retrieve a payload CID for a given
(miner_id, piece_cid)
combination it will then store it in the database.To observe the piece CID indexer two metrics are highly relevant to keep track of.