Skip to content
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

monitoring: Use overall transcode latency in Grafana dashboard #28

Closed
yondonfu opened this issue Jul 8, 2020 · 0 comments · Fixed by #30
Closed

monitoring: Use overall transcode latency in Grafana dashboard #28

yondonfu opened this issue Jul 8, 2020 · 0 comments · Fixed by #30
Assignees

Comments

@yondonfu
Copy link
Member

yondonfu commented Jul 8, 2020

Currently, the Grafana dashboard uses the livepeer_transcode_latency_seconds metric in latency focused graphs. This metric represents the transcode latency from the time the segment is produced from the segmenter until one of the transcoded renditions is received. This metric does not capture latency induced by additional steps after a rendition is received (i.e. waiting for all renditions to be received before playlist insertion and verification when running in on-chain mode). I think using the livepeer_overall_transcode_latency_seconds metric would capture this information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant