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

Test result analytics #2349

Open
howardjohn opened this issue Feb 6, 2020 · 2 comments
Open

Test result analytics #2349

howardjohn opened this issue Feb 6, 2020 · 2 comments
Labels
help wanted Indicates a PR/Issue that needs community help lifecycle/needs-triage Indicates a new PR or issue needs to be triaged

Comments

@howardjohn
Copy link
Member

It would be useful to be able to run queries against historical test rules. The easy way to do this is to download all the logs and use grep and what not, but all the test logs add up to 500gb last I checked.

Some example use cases:

  • Search for a specific error message in logs
  • Find all times a test has failed
  • View pass rate of tests over time
  • View test duration over time
@clarketm
Copy link
Member

clarketm commented Feb 22, 2020 •
edited
Loading

The k8s equivalent for test results analytics is probably triage: https://storage.googleapis.com/k8s-gubernator/triage/index.html. Unfortunately, it is very k8s specific and not reusable. With that being said, we can achieve a similar result with a database, lightweight frontend, and a job to "refresh" the db. But I agree an application for these use cases would be valuable.

@istio-policy-bot istio-policy-bot added the lifecycle/needs-triage Indicates a new PR or issue needs to be triaged label Feb 22, 2020
@clarketm clarketm added help wanted Indicates a PR/Issue that needs community help and removed lifecycle/needs-triage Indicates a new PR or issue needs to be triaged labels Feb 22, 2020
@istio-policy-bot istio-policy-bot added the lifecycle/needs-triage Indicates a new PR or issue needs to be triaged label Feb 22, 2020
@scottilee
Copy link
Contributor

Elasticsearch Kibana might be too heavy weight, could we use Grafana logs?

@howardjohn howardjohn moved this to P2 in Prioritization Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Indicates a PR/Issue that needs community help lifecycle/needs-triage Indicates a new PR or issue needs to be triaged
Projects
Prioritization
Status: P2
Milestone
No milestone
Development

No branches or pull requests
4 participants
@howardjohn @scottilee @clarketm @istio-policy-bot