elastic/kibana

[ResponseOps][Rules] Better message in serverless when the license does not support certain connector types

Open

#201,360 建立於 2024年11月22日

在 GitHub 查看
 (2 留言) (0 反應) (1 負責人)TypeScript (19,065 star) (8,021 fork)batch import
Feature:Alerting/RulesManagementTeam:ResponseOpsgood first issue

描述

In Serverless if you are on the Essentials licensing tier we show the following message for connectors that are not supported by the tier.

Image

In ECS though we show a different message

Image

The message in Serverless is confusing and we should have a message related to the Complete and Essentials licensing tiers.

Related: https://github.com/elastic/kibana/issues/189978

貢獻者指南

技術棧
typescriptreactnodejs
領域
frontendbackend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Familiarity with Kibana licensingUnderstanding of serverless and ECS tiers
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Examine the related issue at https://github.com/elastic/kibana/issues/189978 for context. Look at the code handling license tier messages for connector types, likely in the ResponseOps or Rules UI components. Investigate how the message differs between serverless and ECS and implement a unified message based on the licensing tier.