How to Leverage and Understand Keypup's Various Datasets

Gain insights on leveraging Keypup's datasets to build efficient engineering dashboards. Discover how to query and filter data effectively, monitor performance, and drive success in your software development process. Unlock the power of data-driven decision-making with Keypup.

Celine Nabais
Celine Nabais LinkedIn
• 3 min read
How to Leverage and Understand Keypup's Various Datasets

​Understanding datasets and fields is essential for building efficient engineering dashboards that provide meaningful insights. When working with a powerful tool like Keypup, having a comprehensive understanding of the available datasets and fields enables you to query and filter data effectively. In this article, we will explore how to leverage and understand Keypup's various datasets, helping you to build insightful engineering dashboards tailored to your organization's specific needs.

1. When creating or editing a metric, the first step in the process is to select the dataset that contains the information you want to query. To access the datasets in this specific example, click on the edit (...) button located at the top right of any insight.

Image

2. Then, click on "Edit insight" from the drop-down menu.

Image

‍

3. Now that you're in the "Select dataset" section, click on the dataset drop-down menu, in this case, "Issues & Pull Requests".

Image

4. As you can see, you can select from four different pre-joined datasets that cover most of the possible engineering metrics use cases. Click on any dataset to see which fields you can query and filter on. The available fields of the selected dataset are listed at the right.

Image

5. If you are not sure about the fields and would like to better understand their type, how they are being populated, their source, and more, click on the "Help 👋" button located at the bottom right of your screen.

Image

6. Then, click on the "Help Content" icon located at the top left of the modal.

Image

7. Click on the "Data and Operations" section. From there, you can access all datasets, function, and operator documentation.

Image

8. For this specific tutorial, click on "Issues & Pull Requests dataset".

Image

9. Then, click on "Issues & PRs dataset Overview".

Image

10. A short description of the dataset and its associated fields can be found in this section. You can get a detailed description of any field by clicking on it. For instance, click "Assigned at".

Image

11. A list of details about the field will appear, such as the dataset, field type, description, and source. All articles have a small icon at the top right that allows you to open and enlarge them.

‍

Image

‍

Image

‍

With Keypup's user-friendly interface and comprehensive documentation, you have the tools to leverage and understand datasets more effectively. By building efficient engineering dashboards tailored to your organization's needs, you can monitor performance, identify areas for improvement, and drive success in your software development process.

Discover Keypup's various datasets today to unlock the power of data-driven decision-making in your engineering organization.

Ready to Transform Your Analytics?

Join teams already using AI to make data-driven decisions faster than ever.

Most Recent Articles

The Stale Board: Why Jira Is Always Two Days Behind Your Code

The Stale Board: Why Jira Is Always Two Days Behind Your Code

In a typical enterprise, the Jira board trails Git by almost two business days per issue: code is written before tickets reach "In Progress", and tickets stay open days after their pull requests merge. Learn what engineering leaders on Reddit say about stale boards, status-chasing standups and sprint carryover that exists only on paper, and how Keypup MCP compares each issue's workflow timeline with the commits and merges of its linked pull requests to measure the lag and list the tickets to close.

Thomas Williams
The Time Zone Tax: Why Distributed Teams Lose a Day on Every Code Review

The Time Zone Tax: Why Distributed Teams Lose a Day on Every Code Review

In a typical distributed enterprise, a pull request reviewed from another hub waits 4.1 times longer for a first review, and each round of requested changes costs a day instead of a few hours. Learn what engineering leaders on Reddit say about code review across time zones, and how Keypup MCP measures the time zone tax, from the hour a review request is sent to the teams that review locally and the cross-hub pull requests to hand off before logging off.

Stephane Ibos
The Inner Source Tax: Why Pull Requests to Another Team's Repository Wait Days

The Inner Source Tax: Why Pull Requests to Another Team's Repository Wait Days

In a typical enterprise, a pull request sent to another team's repository waits 3.8 times longer for a first review, takes almost five working days to merge and is three times more likely to be abandoned. Learn what engineering leaders on Reddit say about cross-team contributions, and how Keypup MCP measures the inner source tax, from which owning teams are bottlenecks to which cross-team pull requests to unblock today.

Liam Davis