Joe Reuter

Sounds like a good solution! If I'm understanding correctly, these numbers would only be held in memory, so they would be reset on restart, but that wouldn't matter to us...

> We talked about only tracking metrics per data stream for managed data streams, which would include our integration data streams but not custom ones. Tracking this for non-managed data...

Thanks for the context @salvatore-campagna To summarize: * APM could be used for ES-internal telemetry, but it wouldn't be available on on-prem and it might not be feasible to track...

Thanks Adrien and Salvatore - I agree that this would be enough, updated the description.

@felixbarny We discussed this topic last week with @jbaiera in the ES+Obs sync and concluded that for the time being we can count the docs by looking at index stats...

> If we have all the changes, it would allow Kibana to "stich togehther" the different changes and show it where relevant I can imagine this part getting complicated over...

> I could see this as a low hanging fruit to get started as it at least would allow us to indicate the most recent change, no history. Agreed, this...

@dakrone > We do have these for some of our configuration items (like ILM policies), and we can expand that list fairly easily. There's a little bit of a discussion...

Split out this first step into https://github.com/elastic/elasticsearch/issues/108754

I got the same problem using the inception-v3 network...