Share

Database Cluster Monitoring

Warning:

Local installations of Flow Production Tracking are no longer offered. This documentation is intended only for those with existing instances of Shotgun Enterprise Docker. Click here for a list of our current offerings.

asterisk Contents

It is highly recommended to monitor your Flow Production Tracking cluster to achieve good performance. This is especially true for your database server. Important metrics to gather are:

  • Generic system metrics like CPU, load, memory and disk usage, etc.

  • Context switches

  • Cache hit %

  • PostgreSQL specific metrics

  • Active processes

  • Locks

See the following article for more details and starting points: PostgreSQL Monitoring.

Performance troubleshooting

If you are having performance issues and you think that it’s related to your database server, see this post on performance troubleshooting.

FAQ

What is the PostgreSQL admin password?

When using the configuration script, the password for the Postgres and the Flow Production Tracking user can be found under ~/.pgpass. The same password is used for both users.

I can’t connect to my cluster from an external host.

Make sure that you can do the following:

  • Connect to your cluster using psql, from the database server.

  • psql -h localhost -d postgres -U flow production tracking

  • Make sure you can ping the database server from the host.

  • Validate that your database server firewall is not blocking your connection. You can test by deactivating it temporarily.

  • Validate that your host firewall is not blocking your connection. You can test by deactivating it temporarily.

  • Validate that PostgreSQL is correctly configured to accept incoming connections on all interfaces (see Allow external hosts).

  • Validate that the external host is allowed to connect. If you are using a IP range, make sure your range includes the host.

Was this information helpful?