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
We have already moved 20+ agent-based Observability integrations from experimental or beta to GA. We should keep the momentum going towards the Beats → Agent migration and eventual GA so that we could reduce adoption friction for fleet and agent. Below is the list of packages that should be migrated as a second batch. This list is prioritized according to beats modules' usage telemetry as well as the number of ERs received. Should there be any hinders that prevent a package from moving to GA please highlight them here.
akshay-saraswat
changed the title
Move the second batch of Observability integrations to GA
[Meta] Move the second batch of Observability integrations to GA
Jan 25, 2022
akshay-saraswat
changed the title
[Meta] Move the second batch of Observability integrations to GA
[Meta] Move rest of the Observability agent integrations to GA
Mar 15, 2022
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!
We have already moved 20+ agent-based Observability integrations from experimental or beta to GA. We should keep the momentum going towards the Beats → Agent migration and eventual GA so that we could reduce adoption friction for fleet and agent. Below is the list of packages that should be migrated as a second batch. This list is prioritized according to beats modules' usage telemetry as well as the number of ERs received. Should there be any hinders that prevent a package from moving to GA please highlight them here.
vSphere
IIS
CockroachDB
The text was updated successfully, but these errors were encountered: