Troubleshooting Analytics Support

The Presto server provides a live monitoring dashboard that shows running and completed queries. You can access the dashboard by visiting localhost:8989 in a web browser.

Note that if you're using Datomic Cloud, your access gateway proxy must be running to access the dashboard.

The SQL CLI is recommended for troubleshooting analytics connection and configuration issues.

Launch the CLI in debug mode:

./presto --server <local-ip OR localhost>:8989 --debug

In the debug CLI, run the following system queries:

SHOW SCHEMAS FROM system;

SHOW TABLES FROM system.runtime;

If these queries work correctly, your analytics gateway and analytics system are up and functioning correctly.

If you do not see results from these queries, you should verify your analytics configuration.

If you encounter a schemaName is null error when using the CLI, you may have a catalog or Metaschema configuration issue.

Run the following query in the debug CLI:

SELECT * FROM system.metadata.catalogs;

The results of this query will include all catalogs that are available in the analytics system. Your catalog will be listed in the results. If not, ensure that you have created and synced your catalog properties file correctly. Be sure that you have run sync with the correct directory structure (a catalog and a datomic directory).

Another possible cause of this error is that your Metaschema file is not properly formatted edn or is not correctly located. Also, verify that your Metaschema file ends with a .edn extension.

If you can connect using your catalog and schema, but the expected tables are not displayed, you likely have a misconfiguration of your Metaschema file.

Metaschemas are dynamically associated with Datomic databases. Errors or typos in Metaschemas can prevent association, resulting in the lack of any Presto tables.

• Start the SQL CLI with your catalog and schema names
• Then run the following:

SHOW tables;

At least two tables: db__idents and db__attrs will be displayed, which are both automatically generated for any Datomic database.

• You can examine the contents of these tables with:

SELECT * FROM db__idents;
SELECT * FROM db__attrs;

The contents of these tables indicate the attributes and idents that Datomic analytics was able to read from your Datomic database. If you do not see any additional tables, your Metaschema does not match the schema of this Datomic database.

Ensure that all attributes listed in your Metaschema file exist in your Datomic database (or in the two db__ tables in Presto) and that you have not accidentally mistyped or included an attribute that is not present in your database.