Pull Requests

Seamless integration with your existing workflows
GitHub provides the following definition for a Pull Request: Pull requests let you tell others about changes you've pushed to a branch in a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.

Pull Requests in Metis

We built Metis to seamlessly integrate with your pull requests, requiring minimal changes from the developer's perspective.
After the instrumentation of your code, using Metis SDK, every REST command, SQL command and their execution plan are sent to Metis servers for further analysis. Metis groups all the traces under the source Pull Request who generated them.

Performance Analysis

Every Pull Request can show performance insights. The flow is very similar to the recent activity: show every REST call, SQL, Execution Plans, and their insights. The only difference is the traces generated by the PR are grouped under it. The UI uses a special tag created using a GitHub Action.
Pull Request - Performance Analysis.
for more details on how to instrument the GitGub Action and generate PRs click here.

Schema Migration Analysis

In some cases, adding new features to the application require changes in the schema of the database too. Changing the schema of the DB is also called "Schema Migration".
Changing the schema might cause one of the following problems:
  • Data Loss
  • Application Errors
  • Performance problems
  • Data Quality
  • Security risks
The SQL commands used for changing the schema of the databases are usually stored in a folder. If you are using an ORM then it manages the SQL commands in a folder, usually with a subfolder for each version.
A GitHub Action, dedicated to schema migration analysis, can review all the SQL commands and warn about the impact on the database.
SQL Analysis
To learn how to instrument the GitHub action click here.