Jira¶
Robusta can open Jira tickets based on playbooks results.
Get your Jira configurations¶
To configure the Jira sink you need to have following:
url
: The url of your workspace. For example: https://workspace.atlassian.net (Note: schema (https) is required)username
: Jira workspace user name. For example: jira-user@company.comapi_key
: follow the instructions to get your api key.project_name
: Project for the Jira tickets.issue_type
: [Optional - default:Task
] Jira ticket typededups
: [Optional - default:fingerprint
] Tickets deduplication parameter. By default, Only one issue perfingerprint
will be created. There can be more than one value to use. Possible values are: fingerprint, cluster_name, title, node, type, source, namespace, creation_date etcproject_type_id_override
: [Optional - default: None] If available, will override theproject_name
configurationissue_type_id_override
: [Optional - default: None] If available, will override theissue_type
configuration
Note
The configured user should have the following permissions:
write:jira-work
,read:jira-work
If creating issues by
project_name
orissue_type
fails, try specifying the corresponding ids usingproject_type_id_override
andissue_type_id_override
Configuring the Jira sink¶
CPUThrottlingHigh
and KubePodCrashLooping
Prometheus alerts.Add this to your generated_values.yaml
sinks_config:
- jira_sink:
name: personal_jira_sink
url: https://workspace.atlassian.net
username: username
api_key: api_key
dedups: (OPTIONAL)
- fingerprint
project_name: project_name
match:
identifier: "(CPUThrottlingHigh|KubePodCrashLooping)"
Save the file and run
helm upgrade robusta robusta/robusta --values=generated_values.yaml
You should now get playbooks results in Jira! Example is shown below:
Note
2-way interactivity (CallbackBlock
) isn't implemented yet.