@jranson I took a fresh look at this against current main.

What I see so far:

the prerequisite origin-interface work in Implement Interfacing to support varying Upstream Origin Types #9 is completed;
I do not see an existing Elasticsearch provider or active PR;
reverseproxycache can already proxy/cache selected Elasticsearch HTTP endpoints when configured explicitly, including POST/JSON cache-key fields, but that is not the same as first-class Elasticsearch time-series acceleration.

From #341 and #167, my read is that the unresolved part is likely Grafana-style Elasticsearch queries where Trickster would need to understand the JSON query body, derive a stable cache key with the time range normalized, split/set the requested time range, and model date-histogram-like responses safely.

Before I start implementation work, would you prefer this to be scoped as:

documentation/config examples for using rpc with Elasticsearch where object caching is sufficient,
a minimal first-class Elasticsearch provider targeting Grafana _search / _msearch time-series date histogram queries, including configurable timestamp field support, or
something else entirely?

If option 2 is still the desired direction, I can work up a narrow design and first PR rather than trying to land the whole provider in one large change.

Uh oh!

Support New Origin Type: Elasticsearch #7

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions