elastic/kibana

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

Open

#201360 opened on Nov 22, 2024

View on GitHub
 (2 comments) (0 reactions) (1 assignee)TypeScript (19,065 stars) (8,021 forks)batch import
Feature:Alerting/RulesManagementTeam:ResponseOpsgood first issue

Description

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

Contributor guide

Tech stack
typescriptreactnodejs
Domain
frontendbackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with Kibana licensingUnderstanding of serverless and ECS tiers
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
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.