Kibana: Type naming convention

[arisonl]

A consistent naming convention (e.g. type/name - solution). E.g. in the following screenshot, you can't easily tell which type belongs to which solution.

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[mikecote]

I noticed we have the same issue in the "Select a trigger type" section when creating an alert.

[mikecote]

It was proposed by @mdefazio to group the type filter by application that owns the alert type. It was then brought up by @arisonl that we would still have UX issues in the "Select a trigger type" when creating an alert.

It seems best to simply rename the alert types for 7.7?

A starting point for renaming:

• Error rate threshold
• Index threshold
• Metric threshold
• SIEM Notification
• SIEM Signal
• Transaction duration threshold
• Uptime monitor status

[bmcconaghy]

One thought I have is that we might consider dropping "threshold" as it seems implied in many cases and having so many alerts with that in the name might be confusing.

[mikecote]

That's true. We could just keep threshold wording for index threshold and metric threshold and drop the others:

• Error rate
• Index threshold
• Metric threshold
• SIEM Notification
• SIEM Signal
• Transaction duration
• Uptime monitor status

[mdefazio]

It seems best to simply rename the alert types for 7.7?

Makes sense.

[mikecote]

SIEM alert types to also be sentence case, so:

• Error rate
• Index threshold
• Metric threshold
• SIEM notification
• SIEM signal
• Transaction duration
• Uptime monitor status

I will move forward with this in a PR, thanks everyone!