Document Embedded Cluster telemetry sources in instance data docs#4178
Merged
Conversation
The instance data page only described KOTS and SDK as telemetry sources, with no mention of the EC daemon's lifecycle events or how EC v3 differs from v2 (no KOTS). Also adds a telemetry section to the EC v3 overview and clarifies the kURL caching limitation doesn't apply to EC. sc-136951 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
replicated-ci
added
type::docs
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| #### Embedded Cluster installations | ||
|
|
||
| For Embedded Cluster installations (v2 and v3), there is an additional source of telemetry beyond the SDK and KOTS: the Embedded Cluster daemon running on the host sends lifecycle event data directly to the Vendor Portal. This includes events for installations, upgrades, node joins, and node status changes. |
Contributor
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
|
|
||
| ### From the Embedded Cluster daemon | ||
|
|
||
| For Embedded Cluster installations (v2 and v3), the EC daemon sends lifecycle events to the Vendor Portal as they occur. Unlike the periodic reporting from the SDK and KOTS, these events are sent in real time when an installation, upgrade, or node join starts, succeeds, or fails. |
Contributor
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
|
|
||
| ### From the Embedded Cluster daemon | ||
|
|
||
| For Embedded Cluster installations (v2 and v3), the EC daemon sends lifecycle events to the Vendor Portal as they occur. Unlike the periodic reporting from the SDK and KOTS, these events are sent in real time when an installation, upgrade, or node join starts, succeeds, or fails. |
Contributor
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('are sent').
sgalsaleh
reviewed
Jun 15, 2026
|
|
||
| Which components report telemetry depends on the Embedded Cluster version: | ||
|
|
||
| * **Embedded Cluster v2**: The SDK, KOTS, and the EC daemon all report data. The SDK and KOTS send periodic instance data (version, status, cluster info), while the daemon sends lifecycle events. |
Member
There was a problem hiding this comment.
there is no daemon in EC V2. i guess you mean the EC operator?
sgalsaleh
approved these changes
Jun 15, 2026
sgalsaleh
left a comment
sgalsaleh
left a comment
Member
There was a problem hiding this comment.
LGTM. just the minor comment about the term "daemon" vs "operator". I believe we document it as "operator" in EC V2 docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Preview
Summary
Related: sc-136951
Test plan
/vendor/instance-insights-event-data) resolves correctly####subheading under "Online instances"🤖 Generated with Claude Code