Prom2: /delete instead of /series/drop_series

[gouthamve]

Deletes are almost in tsdb [ref] and now I am looking into implementing in Prometheus itself.

We can delete in time-ranges now instead of a full series drop, keeping that in view series/drop_series is a bad endpoint. Should I make a new /delete end-point with start and end as compulsory parameters?

[fabxc]

I think this now opens a bigger discussion. Our API is essentially entirely read-only aside from /series/drop_series, which is currently disabled in 2.0.

Additionally, we'll want to expose DB administrative APIs ultimately like "pause compaction", "resume compaction", "take snapshot". An HTTP API will be our best bet there as well.

I consider deletes an administrative task as well rather than a core functionality of Prometheus. We should think about moving all those into a separate sub-API, which can easily be turned of via flag or blocked via proxies.

Thoughts on this? Separate admin port? Just a different path?

@brian-brazil

[brian-brazil]

#2173 were my plans for this. TL;DR: Mutating endpoints disabled by flag by default.

[fabxc]

Yes, I'm proposing here to move them all behind a distinct API. That's a) clearer separating purpose and b) more reasonable to implement than having a toggle across random API handlers.

[brian-brazil]

From a security standpoint, having the mutating endpoints under one path would make it easier for users to manage with a reverse proxy.

[gouthamve]

Closed in #2910

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.