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

Searching & clustering traces #22

Open
jonnor opened this issue Jan 6, 2016 · 1 comment
Open

Searching & clustering traces #22

jonnor opened this issue Jan 6, 2016 · 1 comment

Comments

@jonnor
Copy link
Collaborator

jonnor commented Jan 6, 2016

When capturing traces from production environment with lots of processing, one often encounters scenarios where many failures are in fact caused by same bug/issue. And that small changes in inputs often are difference between triggering an issue or not, and that such differences can say a lot about the nature of the bug.

Interesting questions include:

  • How many distinct failure classes exists, and how many of each are there
  • What are the boundary conditions between fail and success

With the ability to upload traces to a service (#2), it becomes interesting to have cloud-based tools which help answer these problem at scale. Performance of making the needed analysis - both how quick to get results, and how much it costs, are key considerations.

References

@jonnor
Copy link
Collaborator Author

jonnor commented Jan 6, 2016

Need to do a review of exiting practices, tools and services that do such things. Some domains that come to mind are:

  • Free text search/indexing
  • Crashdump / stacktrace collecting services

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

No branches or pull requests

1 participant