feat(telemetry): record cloud hosted UUID

[tabVersion]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

https://github.com/risingwavelabs/risingwave-cloud/pull/8212 related pr from cloud side

the pr adjust telemetry behavior: use cloud UUID if provided, use it as trackingID

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[fuyufjh]

Is it possible to unify the cloud & kernel UUIDs? Saying, don't generated any UUIDs when a cloud UUID is provided

[tabVersion]

Is it possible to unify the cloud & kernel UUIDs? Saying, don't generated any UUIDs when a cloud UUID is provided

I don't think so. Since we initially track clusters with tracking_id for telemetry, such migration may take some effort and seem unnecessary.
The requirement here is to track the behavior from cloud hosted clusters, I don't see a strong motivation to migrate to the cloud UUID. We still need to accept reports from on-perm clusters.

[fuyufjh]

Is it possible to unify the cloud & kernel UUIDs? Saying, don't generated any UUIDs when a cloud UUID is provided

I don't think so. Since we initially track clusters with tracking_id for telemetry, such migration may take some effort and seem unnecessary. The requirement here is to track the behavior from cloud hosted clusters, I don't see a strong motivation to migrate to the cloud UUID. We still need to accept reports from on-perm clusters.

I feel you might need to explain again and again to everybody that cloud UUID is not telemetry UUID. Unifying them is the easiest way to avoid this burden.

Also, I said "when a cloud UUID is provided". As the cloud UUID is passed via environment variable, I think it should be easy to write such an if-else.

[fuyufjh]

Hi, is it ready for review?

[fuyufjh]

I think it's probably better to modify the code of generating a tracking ID, such as

risingwave/src/common/src/telemetry/report.rs

Line 68 in 84b7b94

let tracking_id = match info_fetcher.fetch_telemetry_info().await {

Otherwise, the "wrong" tracking ID is still stored in TELEMETRY_TRACKING_ID and it's prone to be misused.