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

Monitor usage in Fedora's CountMe metrics #202

Open
p5 opened this issue Sep 16, 2024 · 3 comments
Open

Monitor usage in Fedora's CountMe metrics #202

p5 opened this issue Sep 16, 2024 · 3 comments

Comments

@p5
Copy link
Member

p5 commented Sep 16, 2024

Our machines are pushing metrics to Fedora's servers.
Bluefin, Aurora and Bazzite are being recorded as separate distros, however I believe UCore is counted under CoreOS.
It would be awesome to see CoreOS' metrics in the Fedora CountMe database.

I think this requires a change to /etc/os-release, but Jorge knows more about how this is setup.

@bsherman
Copy link
Collaborator

@castrojo will you please add info about what we need to make this happen?

@castrojo
Copy link
Member

We just use this service: https://coreos.github.io/rpm-ostree/countme/

Which is available in stock silverblue, we have a systemctl enable rpm-ostree-countme.service in our containerfile.

The os-release stuff is for brew analytics iirc. I am not sure if this service is available in coreos or if it comes with it though.

Copy link

dosubot bot commented Dec 18, 2024

Hi, @p5. I'm Dosu, and I'm helping the ucore team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You raised a concern about UCore being counted under CoreOS in Fedora's CountMe database.
  • @bsherman requested more details, and @castrojo provided insights on the rpm-ostree-countme.service.
  • @castrojo mentioned the /etc/os-release file's role in brew analytics and was unsure about the service's availability in CoreOS.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the ucore repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 14 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Dec 18, 2024
@castrojo castrojo removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Dec 18, 2024
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

No branches or pull requests

3 participants