Lee Hinman

This is an interesting situation, for example, TSDS don't really have a "write index" because documents are routed to the backing index to which their `@timestamp` corresponds. So even deleting...

> I think that for both classic and time-series data streams, it is already not possible to delete the latest generation index. However, for TSDS, (correct me if I'm wrong)...

> Say you have `Index1 (oldest, not writable), Index2 (second oldest, still writable), Index3 (newest index, writable)`, it would not be natural for a user to manually delete Index2. That's...

This is definitely something we'd want to consider as breaking before merging (and should consult the BCC). Also (separately), I wouldn't consider this large enough to introduce a brand new...

> The above sounds a lot like an audit log. How much of this is captured today in audit logs? We already do have an audit log in ES, and...

> Would it be worth it opening a separate more implementation focused issue around that? Yes, that would be useful, to keep this one a bit more focused.

I believe this is a duplicate of #99520, so I'm closing it in favor of that one.

Sure, this is what I see (apologies if I'm missing something, I'm definitely not a Javascript developer):

@fregante I've added you as a collaborator on https://github.com/dakrone/label-test, where ~I've manually created 385 labels so far (I got that far before Github started hitting me with errors about rate-limits)~...

@fregante is there a subset of refined-github that I can disable to avoid this in the short-term? I've had to disable it entirely since I do a lot of daily...