Duansg opened a new pull request, #4233: URL: https://github.com/apache/hertzbeat/pull/4233
## What's changed? When GreptimeDB is not enabled, the observability consoles break with raw errors: log endpoints return 500 with messages like `query log trend aggregate is not supported`, and trace / OTLP metric endpoints return 404 (`ThreeSignalQueryController` is conditional on `warehouse.store.greptime.enabled`). <img width="1282" height="718" alt="capcap-260723-103939" src="https://github.com/user-attachments/assets/362f41b4-c3d6-4e2c-828a-69dbf7faf75e"; /> <img width="1279" height="731" alt="capcap-260723-103954" src="https://github.com/user-attachments/assets/b9c1adda-21de-46f5-a44c-14b7f8de2c7e"; /> This PR: - Adds `HistoryDataReader#supportsLogQuery()` (default false, true for GreptimeDB) and a public `GET /api/observability/capability` endpoint returning `{log, trace, metric}` availability. - Log query endpoints now return a friendly failure message instead of a raw 500 when the storage cannot serve log queries. - The frontend probes the capability at startup (fail-open) and renders a guidance page on the Metrics / Logs / Traces consoles instead of firing doomed requests; menus stay visible. - Adds `observability.storage.unsupported.*` i18n keys for all six locales, unit tests for the new endpoint and the unsupported-storage path. ## Checklist - [x] I have read the [Contributing Guide](https://hertzbeat.apache.org/docs/community/code_style_and_quality_guide) - [ ] I have written the necessary doc or comment. - [x] I have added the necessary unit tests and all cases have passed. ## Add or update API - [ ] I have added the necessary [e2e tests](https://github.com/apache/hertzbeat/tree/master/e2e) and all cases have passed. <img width="1301" height="643" alt="capcap-260723-111008" src="https://github.com/user-attachments/assets/6396fb59-4139-48df-a29e-68ee48bff410"; /> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
