analyze/logs returns 500
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 631
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
- According to the documentation there should be "if ch_cluster else "system.text_log"
https://clickhouse.com/docs/ru/operations/system-tables/text_log system.text_log or returns "POST /api/analyze/logs HTTP/1.1" 500 86 - If I use name CLICKHOUSE_CLUSTER (ch_cluster), it shows 500 other tabs /api/analyze/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in housewatch/clickhouse/queries/sql.py at the linked line and reproduce POST /api/analyze/logs for Kubernetes with and without CLICKHOUSE_CLUSTER. Compare the selected query with the ClickHouse system.text_log documentation; done means the endpoint no longer returns HTTP 500 in the reported configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, kubernetes, python
- Domain
- api, backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100