Specifying Role and Service types
The Role Type and Service Type lists
expect the usual all-caps strings (identifiers) to identify role and service types used in
most other places throughout Cloudera Manager. For example,
OZONE_PROMETHEUS is a role type, and OZONE is a
service type. List elements are separated by the comma character.
Minimum Required Role: Limited Cluster Administrator (also provided by Full Administrator and Cluster Administrator)
Use case examples for Role or Service lists
These lists are applicable in use cases such as routing alerts to the appropriate
teams based on their expertise:
- MGMT (Cloudera Management Service) alerts: Route to personnel experienced in operating Cloudera Manager.
OZONE_PROMETHEUSalerts: Route to monitoring-focused teams.OZONEandHDFSalerts: Route to storage experts.KAFKAalerts: Route to Kafka Subject Matter Experts (SMEs). (This use case is also mentioned in the Sample Custom Alert Script).RANGERalerts: Route to teams concerned with security.
Finding exact Role and Service type values
To find the exact possible all-caps strings (identifiers) to use for Role Types and Service Types, you can perform any of the following actions within Cloudera Manager:
-
Using the Diagnostics filter
-
Inspecting existing Events
- On page, find an event related to the Role Type or Service Type of interest.
- The ROLE_TYPE and SERVICE_TYPE attributes reveal the strings to use.
-
Using the Cloudera Manager API
-
Inspecting Chart Stream Attributes
- On any chart of a Role Type or Service Type of interest, click on a data point.
- The Role Type and Service Type stream attributes contain the required strings.
-
Using Chart Builder type-ahead
