You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The actual work of creating datasources is small (see example) but the initial test resources that create the related monitoring services have to be bootstrapped separately
meshId | string | The unique identifier for the service mesh All control planes running in the same service mesh should specify the same mesh ID. Mesh ID is used to label telemetry reports for cases where telemetry from multiple meshes is mixed together.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked as resolved and limited conversation to collaborators
Dec 19, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add ability to add datasources for:
The actual work of creating datasources is small (see example) but the initial test resources that create the related monitoring services have to be bootstrapped separately
Finishing work from #5058
The text was updated successfully, but these errors were encountered: