Closed flash1293 closed 1 week ago
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)
An alternative approach would be to check for a new k8s cluster name/identifier to show up in the polled datastreams - if a new cluster appears after the onboarding has been started, this is the one we just onboarded and we can show the success message.
@mykolaharmash this is handled by the flow we just merged, right?
@flash1293 yes, it's already part of the flow, so I'll close this one
The existing logs flows detect incoming data via the agent id. In a kubernetes context, it's not possible to feed back the agent id to the onboarding flow in the UI.
To work around this, the kustomize template / k8s manifest should be extended with a processor that adds a custom id to every emitted document. This id is set to the onboarding id, allowing us to monitor the incoming data exclusively for the current onboarding flow.
This is split out as it's not critically important for the functionality.