Telemetry to guide investment decisions

[KnVerey]

As maintainers, we do not currently have a way to gauge feature popularity in the community. This makes it more difficult to identify the most impactful work areas and conversely what we should deprecate. The crawler that previously existed to help with this was removed because it was unmaintained: #3841. Let's resurrect this in some form.

We could also consider an opt-in mechanism to report feature usage at build time. This has serious privacy implications to consider.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[KnVerey]

Related to #4148

[natasha41575]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[natasha41575]

/reopen
/lifecycle frozen

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[annasong20]

/triage accepted

[natasha41575]

For whoever is going to pick up this issue, I think there are a few steps here:

1. Write up a proposal for what metrics we are interested in. For example, how many kustomization files there are on Github, the popularity of different fields, what kinds of custom plugins are people writing etc
2. Take a look at the existing Github crawler and understand how it works and what kinds of metrics does it provide, are these useful and can the crawler be enhanced to support other metrics we might be interested in
3. (Optional) Research other possible ways that we might be able to collect metrics and weigh pros and cons of each.

[natasha41575]

@valaparthvi I am hoping you can work on this! I can't assign you the issue but please assign it to yourself if you can.

[valaparthvi]

/assign valaparthvi

[valaparthvi]

In my previous experience with Telemetry collection, I used Segment to collect the telemetry data, and then pass the data to Woopra to analyze the collected data.

Segment provides a Go library, even though the library is not actively maintained, I have seen that it is functional as is.

Ref:

• https://segment.com/pricing
• https://www.woopra.com/pricing
• https://github.com/segmentio/analytics-go

[antoooks]

@valaparthvi Found an interesting paper about correlation between potential project metrics and project impact. It shows that category of metrics classified under activity metrics shows positive correlation to project impact. With impact measured using number of other projects that uses the project as an upstream or downstream dependency, this is where the crawler is needed.

Source: https://digitalcommons.unomaha.edu/cgi/viewcontent.cgi?article=1061&context=isqafacpub

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted