Roshan Gonsalkorale

Cheers @smith, Perhaps it makes sense to tackle each asset at a time (e.g. when we start looking at containers...we'd audit them)? If that works, I think we could incorporate...

Hey everyone, Looking at this to get an understanding of the issue here. Replaying back the problem to check I understand correctly: # Current State ### APM > Infrastructure (beta)...

Completely missed this @neptunian - sorry for the delay. @smith / @neptunian - What do you think about an epic to start tackling 'containers' in our roadmap? Perhaps some discovery...

Cool - I created this epic in the backlog for discovery later: - [ ] https://github.com/elastic/obs-infraobs-team/issues/1198

Closing as we've either solved part of this already or are planning to fix this in the near future. We'll refer to this issue in the work that we do...

Hey @iblancof - do we think your fix will improve this situation?

Closing this issue based on the [above](https://github.com/elastic/kibana/issues/98617#issuecomment-2296039341)

@smith - here is the bug. This feels like it should be a high priority in serverless to me. WDYT?

@vinaychandrasekhar FYI (cc @grabowskit)

@chrisdistasio FYI this is something users are likely to see if they try and create anomaly detection jobs via the Infra UI in serverless... **Note** : this is pretty related...