# Blogs

### 2020/04/27 [Introducing Apache Pinot 0.3.0](https://engineering.linkedin.com/blog/2020/apache-pinot-030-update)

### 2020/04/10 [Using Apache Pinot and Kafka to Analyze GitHub Events](https://medium.com/apache-pinot-developer-blog/using-apache-pinot-and-kafka-to-analyze-github-events-93cdcb57d5f7)

### 2020/02/20 [Analyzing anomalies with ThirdEye](https://engineering.linkedin.com/blog/2020/analyzing-anomalies-with-thirdeye)

### 2020/01/15 [Engineering SQL Support on Apache Pinot at Uber](https://eng.uber.com/engineering-sql-support-on-apache-pinot/)

### 2019/07/11 [Auto-Tuning Pinot Real-Time Consumption](https://engineering.linkedin.com/blog/2019/auto-tuning-pinot)

### 2019/06/14 [Star-Tree Index: Powering Fast Aggregations on Pinot](https://engineering.linkedin.com/blog/2019/06/star-tree-index--powering-fast-aggregations-on-pinot)

### 2019/06/03 [Smart Alerts in ThirdEye, LinkedIn’s Real-Time Monitoring Platform](https://engineering.linkedin.com/blog/2019/06/smart-alerts-in-thirdeye--linkedins-real-time-monitoring-platfor)

### 2019/03/12 [Pinot Joins Apache Incubator](https://engineering.linkedin.com/blog/2019/03/pinot-joins-apache-incubator)

### 2019/01/09 [Introducing ThirdEye: LinkedIn’s Business-Wide Monitoring Platform](https://engineering.linkedin.com/blog/2019/01/introducing-thirdeye--linkedins-business-wide-monitoring-platfor)

### 2017/09/26 [Engineering Restaurant Manager, our UberEATS Analytics Dashboard](https://eng.uber.com/restaurant-manager/)

### 2015/06/10 [Open Sourcing Pinot: Scaling the Wall of Real-Time Analytics](https://engineering.linkedin.com/pinot/open-sourcing-pinot-scaling-wall-real-time-analytics)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pinot.apache.org/release-1.1.0/resources/blogs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.