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.

Sign up for GitHub

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

Jump to bottom

Metrics / Tracing: What are they good for? #1032

Open
Chickensoupwithrice opened this issue Aug 1, 2023 · 2 comments
Open

Metrics / Tracing: What are they good for? #1032

Chickensoupwithrice opened this issue Aug 1, 2023 · 2 comments
Assignees
@Chickensoupwithrice
Labels
investigation Research and/or prototyping before dev work ops/deployment Related to deployment of Browsertrix Cloud

Comments

@Chickensoupwithrice
Copy link
Contributor

One thing I'd like to work on for Browsertrix is some sort of metrics implementation. There have been past attempts at getting metrics working (specifically k8s metrics server for cpu / mem utilization) but since nobody is using them it's fairly useless. This issue is to catalogue use cases for metrics on Browsertrix.

Thoughts:

  • We could import metrics into the WACZ, and could help with QA?
  • We already have a kube-metrics server, but it's kinda useless, we need a strong why
  • Storage Metrics?
  • Archived Data Metrics?
  • App metrics (crawl duration, resource utilization, etc)

it's an interesting challenge because Browsertrix is made up of quite a few smaller components (crawler, replay webpage, front / back end) and it isn't clear which components would benefit from having tracing or metrics implemented for them, and what visibility they would grant to browsertrix.
@Chickensoupwithrice Chickensoupwithrice added ops/deployment Related to deployment of Browsertrix Cloud investigation Research and/or prototyping before dev work labels Aug 1, 2023
@Chickensoupwithrice Chickensoupwithrice self-assigned this Aug 1, 2023
@Chickensoupwithrice Chickensoupwithrice moved this from Triage to Design In Progress in Webrecorder Projects Aug 1, 2023
@ikreymer ikreymer moved this from Design In Progress to Todo in Webrecorder Projects Aug 1, 2023
@Shrinks99
Copy link
Member

As a designer, UI interaction metrics are really helpful for gauging which parts of your app users interact with the most and (at a more detailed level) which actions are accomplished in the same order often. Would be super jazzed to see the first part and it would help me out!

@Shrinks99
Copy link
Member

RE: Crawling metrics, something that we discussed a while ago that is worth noting here is possible integration of Wappalyzer as a method of diagnosing if crawling / replay issues are related to certain web technologies.

@Chickensoupwithrice Chickensoupwithrice mentioned this issue Aug 17, 2023
Closed
@Shrinks99 Shrinks99 mentioned this issue Aug 21, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Chickensoupwithrice Chickensoupwithrice

Labels
investigation Research and/or prototyping before dev work ops/deployment Related to deployment of Browsertrix Cloud
Projects
Webrecorder Projects
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Shrinks99 @Chickensoupwithrice