Loggr Query Language

So your posting all your valuable event data to Loggr. Your data is safe and accessible through our tools, but you own your data and we know how important it is to have full control and access to it. Whether you want to integrate it into other business applications, perform deeper analysis, archive it or simply move it to a different service, we make it pretty easy to do.

One of the tools we provide for digging through your events is a custom query language. We call it the Loggr Query Language (or LQL). It’s a very simple language similar to SQL that can be used in our API or within the query editor on the website.




You can also run queries through the Loggr Web API using the Query endpoint.

The query syntax is:



Some examples. First, to get the text from the last 5 events added to your log.


This next example uses a WHERE clause to get the last 5 events that have text matching ‘New subscriber’ exactly.


Using the same query above, but replace the exact match on text with a regex match clause LIKE. Also, this time we’re going to return just the KEY for the event which we can use to call into the API for more specifics about the event.


The following queries based on a set of tags. It also return the created date and geo info for each event.


You can also include boolean operators in the WHERE clause.


Finally a more complex example showing how you can query for aggregate information and specify time ranges. This query gets the sum of all events of class ‘order’ having the tag ‘online’. It uses the OCCURS clause to get the aggregates over the last 7 days. It will return the results as a list of 7 records for each day in the query. Each record will contain the KEY (in this case, the date) and the SUM.


If you want to get specific dates, you can include them in the OCCURS clause instead of the keywords shown above.