Dynamic Data Set
Before we deploy the Query Engine, we need to build our smart proxy logic to forward on requests.
The config defines one or more data sets that you will make available on the dashboard. You can either define it using a SQL statement, or by referencing tables and fields along with instructions on how the tables are joined together.
Each integration has its own config definition, find the one that applies to you, and start building! For this example, we advise you manually craft a config to see how dynamic configs would work, before writing the code to dynamically generate the configs.
If you wish to find examples of configs, you can do so in our GitHub examples repo (opens in a new tab)!
To make this work in production, you will need to set the
queryEngineEndpoint property of the dashboard to an endpoint on your own servers.
This endpoint will then need to proxy the requests onto your deployed Vizzly Query Engine.
For all POST requests that include the
Content-Type header with a value including
application/json, you will need to add the dynamic config to the request body under the top-level key
For all requests being proxied to the Query Engine, you will need to set the
Config-Api-Key header. The value of which we will create later in this tutorial.
The process for setting up a dynamic Query Engine differs from the standard process. Next, we'll go through these steps