phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <>
Subject Re: [DISCUSS] Design for a "query log"
Date Fri, 02 Mar 2018 01:05:25 GMT
Any feedback from folks? Not sure if the silence should be interpreted
as ambivalence or plain old being busy :)

On Mon, Feb 26, 2018 at 4:57 PM, Josh Elser <> wrote:
> Hiya,
> I wanted to share this little design doc with you about some feature work
> we've been thinking about. The following is a Google doc in which anyone
> should be allowed to comment. Feel free to comment there, or here on the
> thread.
> The high-level goal is to create a construct in which Phoenix clients will
> automatically serialize information about the queries they run to a table
> for retrospective analysis. Ideally, this information would be stored in a
> Phoenix table. We want this data to help answer questions like:
> * What queries are running against my system
> * What specific queries started between 535AM and 620AM two days ago
> * What queries are user "bob" running
> * Are my user's queries effectively using the indexes in the system
> Anti-goals for include:
> * Cluster impact (computation/memory) usage of a query
> * Query performance may be slowed to ensure all data is serialized
> * A third-party service dedicated to ensuring query info is serialized (in
> the event of client failure)
> Take a look at the document and let us know what you think please. I'm happy
> to try to explain this in greater detail.
> - Josh (on behalf of myself, Ankit, Rajeshbabu, and Sergey)

View raw message