Frequently Asked Questions
If the locally running database that you want to connect to runs in a Docker container:
- 1.Run:
docker inspect - 2.In the
networkssection of the results, find the Gateway IP address. Use this IP address as the server address in Tonic.
If the locally running database does NOT run in a container, but runs on the machine, then:
- On Windows or Mac, use
host.docker.internal - On Linux, use
172.17.0.1, which is the IP address of thedocker0interface.
If you use Tonic Cloud, and your database only allows connections from allowlisted IP addresses, then you need to allowlist Tonic static IP addresses.
- 54.92.217.68
- 3.217.201.126
- 52.22.13.250
- 18.159.127.160
- 3.69.249.144
You must allowlist api.amplitude.com, which is used for our telemetry. See the Amplitude site for more information.
These metrics are valuable for us as we debug, make product roadmaps, and determine feature viability.
No customer data is included.
To support the one-click update option, Tonic needs to be able to retrieve information about the latest Tonic version.
Click your user image at the top right. The menu includes the Tonic version.
We recommend that you use a static copy of your production database that was restored from a backup.
If that's not possible, consider the following when you connect Tonic to your source data:
- Tonic cannot guarantee referentially integrity of the output data if the source database is written to while data is generated. For this reason we recommend that you connect to a static copy of production data.
- Read replicas and fast followers can be problematic for Tonic because of how long it takes some queries run. Read replicas tend to have short query timeout limits, which causes the queries to timeout. Read replicas also reflect recent writes, which means that we cannot guarantee the referential integrity of the output.
For details about the types of data that Tonic does and does not collect, see Data that Tonic collects.