[feature] add datasource status retrieval and update alert settings UI #3985
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support for dynamically detecting and displaying the availability of query executors (PromQL, SQL) for periodic alerts in the alert settings UI. It improves the user experience by disabling or enabling periodic alert options and query language choices based on backend executor configuration, and provides contextual descriptions and tooltips for query languages. Several UI improvements and backend API additions support these changes.
Backend: Executor Status API and Service Enhancements
getAvailableExecutors()toDataSourceServiceand its implementation, which checks and returns the availability of PromQL and SQL executors. This enables the frontend to determine which query languages are supported for periodic alerts. [1] [2]/datasource/statustoAlertDefineControllerto expose executor status to the frontend. [1] [2] [3]Frontend: Alert Setting UI and Logic Improvements
Internationalization and Usability
API Integration
AlertDefineServicefor fetching executor status from the new backend API.