โœ•

Join us at KubeCon + CloudNativeCon North America, Nov 7-9 in Chicago! Swing by Booth L26 for exclusive SWAG ๐ŸŽ

โœ•
Skip to content
On this page

Subscribe to our newsletter

Get the latest dates and news about GreptimeDB.
Biweekly
โ€ข
May 24, 2023

Biweekly Report (May.8 - May.21) โ€“ Tokio Console Enabled for Easier Troubleshooting

A recap of the past two-weeks progress and changes happened on GreptimeDB.

Summary โ€‹

Together with all our contributors worldwide, we are glad to see GreptimeDB making remarkable progress for the better. Below are some highlights:

  • Support TQL EXPLAIN / TQL ANALYZE clauses
  • Enable tokio console
  • Support more endpoints for Prometheus HTTP API

Contributor list: (in alphabetical order) โ€‹

For the past two weeks, our community has been super active with a total of 8 PRs from 6 contributors merged successfully and lots pending to be merged. Congrats on becoming our most active contributors in the past 2 weeks:

๐Ÿ‘ Let's welcome @gitccl and @Taylor-lagrange as the new contributors to join our community with their 2 PRs merged respectively.

Special thanks to @etolbakov, for continuously contributing to our projects, with 14 out of 15 open PRs successfully merged๏ผThank you for your generous and brilliant contributions!

A big THANK YOU for all our members and contributors! It is people like you who are making GreptimeDB a great product. Let's build an even greater community together.

Highlights of Recent PR โ€‹

Support for TQL EXPLAIN and TQL ANALYZE clauses โ€‹

  • TQL EXPLAIN (similar to EXPLAIN from SQL) doesn't execute the query but tells how the query would be executed.
  • TQL ANALYZE (similar to ANALYZE from SQL) executes the plan and tells the detailed per-step execution time.

Enable Tokio console โ€‹

With the integration of tokio-console and GreptimeDB, as detailed in the Greptime Developer Guide, all tokio tasks can now be seamlessly displayed. This enhancement significantly aids in troubleshooting issues related to the tokio runtime.

Tokio console screenshot:

screenshot-of-tokio-console

Support for additional endpoints in Prometheus HTTP API โ€‹

In addition to query and query_range endpoints, as Prometheus HTTP API describes, there are some other useful endpoints which will help Prometheus users to explore the metadata or details of the datasets. These endpoints will facilitate the seamless integration of GreptimeDB into various systems as a Prometheus service.

Here's an example:

rust
curl 'localhost:9090/api/v1/labels'
{
    "status": "success",
    "data": [
        "__name__",
        "call",
        "code",
        "config",
        "dialer_name",
        "endpoint",
        "event",
        "goversion",
        "handler",
        "instance",
        "interval",
        "job",
        "le",
        "listener_name",
        "name",
        "quantile",
        "reason",
        "role",
        "scrape_job",
        "slice",
        "version"
    ]
}

These are the updates of GreptimeDB and we are constantly making progress. We believe that the strength of our software shines in the strengths of each individual community member. Thanks for all your contributions.

New things โ€‹

GreptimeDB v0.3 is ready for release in early June โ€‹

We are excited to announce that GreptimeDB v0.3 is ready for release in early June! This forthcoming iteration is an initial distributed version, providing users with an opportunity to test its capabilities firsthand.

This release will spotlight region-level high availability servicesโ€”an assurance that data reliability will be achieved in subsequent releases. It will also introduce distributed queries for key scenarios, with a particular focus on PromQL query aspects. Moreover, we are committed to delivering a write performance that not only matches but potentially outpaces that of mainstream databases.

GreptimeDB Community is now open-sourced, welcome to contribute โ€‹

We extend an invitation to everyone to stay abreast of our updates and await the opportunity to trial GreptimeDB v0.3. Thank you for your support and anticipation!

In order to promote collaboration across teams and create a good culture within the Greptime community, it's important to have documented community guidance so that members can build trust faster and focus on long-term sustainable growth of our community.

Whether you're a developer, architect, designer, technical writer, or just someone passionate about open-source projects, there's a place for you in our community; Check more details here: https://github.com/GreptimeTeam/Community.

If you have any suggestions for improving this guide, you can either raise PRs or submit a proposal of improvement by sending us an email [email protected]. We welcome you to share your ideas and help us build a vibrant and inclusive community!

Join our community

Get the latest updates and discuss with other users.

Subscribe to our newsletter

Get the latest dates and news about GreptimeDB.