Documentation for visualizing ClickHouse data in Hashboard

[dse0]

No description provided.

[CLAassistant]

All committers have signed the CLA.

[mshustov]

could you add Hashboard to https://github.com/ClickHouse/clickhouse-docs/blob/60272cea481e0a73b6443348a3bc660e033ff8f6/docs/en/integrations/index.mdx ?

[dse0]

Done 👍

[mshustov]

Could you add import ConnectionDetails from '@site/docs/en/_snippets/_gather_your_details_native.md'; and <ConnectionDetails /> snippet? See an example https://raw.githubusercontent.com/ClickHouse/clickhouse-docs/main/docs/en/integrations/data-visualization/grafana-and-clickhouse.md

[dse0]

Done 👍

[robot-clickhouse-ci-1]

This is an automated comment for commit 2b76d50 with description of existing statuses. It's updated for the latest CI running

✅ Click here to open a full report in a separate page

Successful checks

Check name	Description	Status
CI running	A meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR	✅ success
Docs Check	Builds and tests the documentation	✅ success
Mergeable Check	Checks if all other necessary checks are successful	✅ success
Vercel	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success

[mshustov]

@justindeguzman for some reason, I don't have access to Docs check logs. Could you provide more details on the CI check failure?

[justindeguzman]

Just upgraded role @mshustov, the deploys should go through now

[mshustov]

@justindeguzman can we relax the requirements for the stale merges? I can't merge the PR since This branch is out-of-date with the base branch. We don't write rights to the forks (it should be allowed explicitly).
Asking a contributor to constantly merge the main branch or provide ClickHouse team write access to the fork, highers the contribution bar

[dse0]

I went ahead and merged main again, looks like the PR needs re-approval? @mshustov I gave you write access to the fork if it's helpful.