-
Notifications
You must be signed in to change notification settings - Fork 17
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
Define implementation of adoption metrics #149
Define implementation of adoption metrics #149
Conversation
Overall the simplest solution is the Grafana option. It will be quite challenging if we want to | ||
make our dashboard publicly visible but it's still easier than gathering the data and displaying | ||
them by ourselves (dashboard option). |
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.
+1
|
||
Cons: | ||
|
||
- visibility: only internal folks will be able to see the graphs (since our current dashboard |
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.
I understand this epic to serve mostly our team and colleagues in Red Hat. Am I missing something or is there a requirement that the charts should be publicly accessible?
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.
- If we can do it publicly, why not do that publically.
- Public service can be easier to access also for internal people.
- Packit marketing.
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.
Yes, the point is that it would be great to have this data publicly available (for the reasons Franta mentioned above), but it's not necessary (from the key functionality point of view). So there is an option to implement key functionality and later make this data publicly available (using the steps outlined in the PR)
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.
Exactly. Let's start with the private Grafana and make a public view as a second step.
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.
I am still inclined to have it public if possible but I see the implementation troubles -- I am for the Grafana dashboard as a first step and try to make it public (e.g. via methods you've described) as a second step.
bf11670
to
952d5a0
Compare
No description provided.