We’re working on other monitoring tools, but for now there are a few tools you can use for troubleshooting issues with Materialize Cloud.
Third-party monitoring tools
You can check on the status of Materialize systems at https://status.materialize.com. You can also sign up at the page to be notified of any incidents through email, text, Slack, or Atom or RSS feed.
The Metrics card shows memory and CPU utilization for different ranges of time, and offers access to logs.
Materialize periodically emits messages to its log file. You can view these logs in the Metrics card on the Deployments page. Click View logs beneath the utilization graph, then click Download if you want to save the logs for review.
These log messages serve several purposes:
- To alert operators to critical issues
- To record system status changes
- To provide developers with visibility into the system’s execution when troubleshooting issues
We recommend that you monitor for messages at the
levels. Every message at either of these levels indicates an issue
that must be investigated and resolved.
For more information, see Monitoring: Logging
Disabling user indexes
If your Cloud deployment unexpectedly consumes all CPU or memory, you can troubleshoot by restarting with indexes on user-created objects disabled.
To do so:
Go to the Deployment details page and click Edit.
Open the Advanced settings section and click Disable User indexes, then click Save.
The deployment will restart automatically.
In this mode users…
- Can access objects within the system catalog to help determine which indexes are causing the crash.
- Can only
SELECTfrom user-created objects that do not rely on user-created indexes. In essence, this means users can still
- Tables, but they will never return any data.
- Views that contain only references to constant values or depend entirely on system tables' indexes.
INSERTdata into tables.
- Can create new objects, but any created indexes are disabled.
After troubleshooting any issues, you can enable individual indexes or restart Materialize without disabling user indexes to enable all indexes at once.
For assistance with this mode, see: