Troubleshooting: Provide concise troubleshooting guidelines

[amotl]

Problem

When encountering troubles with CrateDB database clusters, for example by observing any anomalies, there is no clear and complete information publicly available about the whole procedure to find out about potential root causes and whatnot.

Solution

With optional tool support, let's improve corresponding documentation on this matter. This patch makes a start on it, and invites you to contribute and collaborate. Feel free to add patches, or share any suggestions which come to mind as we go.

Preview

Before vs. after.

/cc @karynzv, @hlcianfagna, @hammerhead, @mkleen, @surister, @seut, @proddata, @simonprickett

[hammerhead]

What is the approach to keep these links to release bundles up-to-date? I noticed it currently links to a specific GitHub Action run. Is there a possibility to have the artifacts as part of the regular release assets (https://github.com/crate-workbench/cratedb-toolkit/releases), so updating it here is just a matter of keeping it in sync with the latest cratedb-toolkit version number?

[amotl]

Thanks, this is right on the spot. Currently, there is no solid approach yet, we just did the minimum things to establish a build matrix through a corresponding GitHub Actions workflow.

I've provided a relevant response citing you on the corresponding tracking ticket, so it will not get lost when merging this patch.

• Build self-contained native binaries cratedb-toolkit#160 (comment)

We will need to improve the situation with subsequent iterations.

[hammerhead]

There are some questionable (and partly also broken) queries on sys tables mentioned (example: SELECT _node['name'], _node['hostname'], * FROM sys.operations;). But since they already existed before, and this PR doesn't touch them, I'm ok with merging and doing another iteration.

[amotl]

More details within the SQL statements in the system-tables page had to be fixed. 4b9fc77 now includes all of them, including yours. Thanks!