How Can Metis Help?
Stay ahead of the game: Catch DB issues before they catch you.
You can implement Metis in a few different ways to ensure it fits with the rest of your tech stack seamlessly, and that it respects the privacy of your organization's data. Our engineers worked hard to simplify the instrumentation process and minimize the impact on performance.
An Illustration of how Metis is integrated at different stages of development
Metis can help with different problems at any step of the software development lifecycle
- Analyze a single SQL Command
- Predict the impact of new changes in the app on the production DB by analyzing the SQL commands generated during QA tests
- Analyze the planned changes in the database schema (also known as schema migration)
- Analyze the schema of the database
AFTER the deployment of the new version
Monitor the Production environment, focusing on the queries recently added
General monitoring of the Production environment.
Quickly analyze an SQL command using the web app Query Analyzer. Just provide the SQL command and its execution plan. No need to install anything as the analysis is done from the web. No need to connect to the database, as all the analysis is done using the execution plan.
The most basic form of analysis Metis offers is done locally on the developers machine.
You can connect provide Metis a connection to any database with the same schema as your production database, and test the efficiency of queries without actually running them and affecting your database performance or data.
If you have unit or integration tests running as part of your CI/CD which interact with a database, you can get a report summarizing your database interactions efficiency, issues and the steps required to fix them.
For your convenience we offer an SDK and GitHub Workflows, to ease integration and present reports inside your pull request page.
Metis offers two ways to observe your production database in order to analyze performance.
Production Metadata Collector (PMC)
For those who don't want to install extra SDKs in their production server, we offer another solution.
By setting up the PMC, you enable Metis to collect metadata such as the general structure, usage and statistics of the production database. Metis can then be configured to simulate how different SQL Commands would run in production without affecting production performance, or running the risk of exposing production data.
As developers, we know how intimidating it can be to change your database schema while being live.
Having a PMC configured enables Metis to detect upcoming changes in database schemas that can potentially break production. Metis then alerts you, and gives you the solution to remediate the issue.
Last modified 3h ago