Vh6ddlmZmZmZeZdZdZddlZddl m Z ddl m Z ddl mZmZmZddlmZde fd Z dd Z dd Zd Zed k(reyy))absolute_importdivisionprint_functiona[ module: pagerduty_alert short_description: Trigger, acknowledge or resolve PagerDuty incidents description: - This module will let you trigger, acknowledge or resolve a PagerDuty incident by sending events. author: - "Amanpreet Singh (@ApsOps)" - "Xiao Shen (@xshen1)" requirements: - PagerDuty API access extends_documentation_fragment: - community.general.attributes attributes: check_mode: support: full diff_mode: support: none options: name: type: str description: - PagerDuty unique subdomain. Obsolete. It is not used with PagerDuty REST v2 API. api_key: type: str description: - The pagerduty API key (readonly access), generated on the pagerduty site. - Required if O(api_version=v1). integration_key: type: str description: - The GUID of one of your 'Generic API' services. - This is the 'integration key' listed on a 'Integrations' tab of PagerDuty service. service_id: type: str description: - ID of PagerDuty service when incidents will be triggered, acknowledged or resolved. - Required if O(api_version=v1). service_key: type: str description: - The GUID of one of your 'Generic API' services. Obsolete. Please use O(integration_key). state: type: str description: - Type of event to be sent. required: true choices: - 'triggered' - 'acknowledged' - 'resolved' api_version: type: str description: - The API version we want to use to run the module. - V1 is more limited with option we can provide to trigger incident. - V2 has more variables for example, O(severity), O(source), O(custom_details) and so on. default: 'v1' choices: - 'v1' - 'v2' version_added: 7.4.0 client: type: str description: - The name of the monitoring client that is triggering this event. client_url: type: str description: - The URL of the monitoring client that is triggering this event. component: type: str description: - Component of the source machine that is responsible for the event, for example C(mysql) or C(eth0). version_added: 7.4.0 custom_details: type: dict description: - Additional details about the event and affected system. - A dictionary with custom keys and values. version_added: 7.4.0 desc: type: str description: - For O(state=triggered) - Required. Short description of the problem that led to this trigger. This field (or a truncated version) will be used when generating phone calls, SMS messages and alert emails. It will also appear on the incidents tables in the PagerDuty UI. The maximum length is 1024 characters. - For O(state=acknowledged) or O(state=resolved) - Text that will appear in the incident's log associated with this event. default: Created via Ansible incident_class: type: str description: - The class/type of the event, for example C(ping failure) or C(cpu load). version_added: 7.4.0 incident_key: type: str description: - Identifies the incident to which this O(state) should be applied. - For O(state=triggered) - If there is no open (in other words unresolved) incident with this key, a new one will be created. If there is already an open incident with a matching key, this event will be appended to that incident's log. The event key provides an easy way to 'de-dup' problem reports. If no O(incident_key) is provided, then it will be generated by PagerDuty. - For O(state=acknowledged) or O(state=resolved) - This should be the incident_key you received back when the incident was first opened by a trigger event. Acknowledge events referencing resolved or nonexistent incidents will be discarded. link_url: type: str description: - Relevant link URL to the alert. For example, the website or the job link. version_added: 7.4.0 link_text: type: str description: - A short description of the O(link_url). version_added: 7.4.0 source: type: str description: - The unique location of the affected system, preferably a hostname or FQDN. - Required in case of O(state=trigger) and O(api_version=v2). version_added: 7.4.0 severity: type: str description: - The perceived severity of the status the event is describing with respect to the affected system. - Required in case of O(state=trigger) and O(api_version=v2). default: 'critical' choices: - 'critical' - 'warning' - 'error' - 'info' version_added: 7.4.0 ag - name: Trigger an incident with just the basic options community.general.pagerduty_alert: name: companyabc integration_key: xxx api_key: yourapikey service_id: PDservice state: triggered desc: problem that led to this trigger - name: Trigger an incident with more options community.general.pagerduty_alert: integration_key: xxx api_key: yourapikey service_id: PDservice state: triggered desc: problem that led to this trigger incident_key: somekey client: Sample Monitoring Service client_url: http://service.example.com - name: Acknowledge an incident based on incident_key community.general.pagerduty_alert: integration_key: xxx api_key: yourapikey service_id: PDservice state: acknowledged incident_key: somekey desc: "some text for incident's log" - name: Resolve an incident based on incident_key community.general.pagerduty_alert: integration_key: xxx api_key: yourapikey service_id: PDservice state: resolved incident_key: somekey desc: "some text for incident's log" - name: Trigger an v2 incident with just the basic options community.general.pagerduty_alert: integration_key: xxx api_version: v2 source: My Ansible Script state: triggered desc: problem that led to this trigger - name: Trigger an v2 incident with more options community.general.pagerduty_alert: integration_key: xxx api_version: v2 source: My Ansible Script state: triggered desc: problem that led to this trigger incident_key: somekey client: Sample Monitoring Service client_url: http://service.example.com component: mysql incident_class: ping failure link_url: https://pagerduty.com link_text: PagerDuty - name: Acknowledge an incident based on incident_key using v2 community.general.pagerduty_alert: api_version: v2 integration_key: xxx incident_key: somekey state: acknowledged - name: Resolve an incident based on incident_key community.general.pagerduty_alert: api_version: v2 integration_key: xxx incident_key: somekey state: resolved N) AnsibleModule) fetch_url)urlparse urlencode urlunparse)datetimecd}dd|zdd} |ddd} |r|| d <tt|} t| d | d <t| }|||d | \} } | ddk7r|j d| dzt j | jd}d}t|dk(r |dvr|dfS|d fS||ddk7r|dd fS|ddfS)Nz#https://api.pagerduty.com/incidentsapplication/jsonzToken token=%sz(application/vnd.pagerduty+json;version=2) Content-type AuthorizationAcceptzincident_number:descUTC)z service_ids[]sort_by time_zone incident_keyTget)methodheadersstatusz2failed to check current incident status.Reason: %smsgr incidentszNo corresponding incidentr) acknowledgedresolvedF) listrr r fail_jsonjsonloadsreadlen)modulenamestate service_idintegration_keyapi_keyr http_callurlrparams url_partsresponseinforrs u/home/dcms/DCMS/lib/python3.12/site-packages/ansible_collections/community/general/plugins/modules/pagerduty_alert.pycheckr3s /C*)G3<G$)F !-~Xc]#IVT*IaL Y Cvs5'JNHd H~*,0K8 9 8==?+K8I %C 9~ 0 0: Dy )A,x( (|T!! Q< c d}ddi}||||||d} t||d|tj| \} } | ddk7r|jd |d | d  tj| j } | S) NzAhttps://events.pagerduty.com/generic/2010-04-15/create_event.jsonrr ) service_key event_typer descriptionclient client_urlpostrrdatarr failed to . Reason: rr)rr"dumpsr!r#r$) r&r6r7descrr9r:r-rr=r0r1json_outs r2 send_event_v1rC s MC*G # $  Dvs6'.TZZ5EGNHd H~$d5k3 4zz(--/*H Or4c Hd}ddi} |||||d} |r|g| d<|r|| d<|dk7r| jdt||d | tj|  \} } | d d k7r|j d |d| dtj | j } | dfS)Nz'https://events.pagerduty.com/v2/enqueuerr ) routing_key event_actionpayloadr9r:links dedup_keytriggerrGr;r<rr>r?rrT)poprr"r@r!r#r$)r&r6r7rGlinkrr9r:r-rr=r0r1rBs r2 send_event_v2rN&s 3C*G#"  D W ([Y vs6'.TZZ5EGNHd H~$d5k3 4zz(--/*H T>r4c ttd1idtdtddtddtdtddtdgd  d td d d dgdtdtdtdtddtddtdtddtdtdtdtd gd!"d d ddgfdd#dgfdd$dgfgd%gd&}|jd}|jjd}|jjd}|jjd}|jjd}|jjd}|jjd}|jjd}|jjd} |jjd} | |jjdt j j |jjd|jjd|jjd|jjdd'} i} |jjdrW|jjd| d(<|jjdr|jjd| d)<||}|jd*d+d,d-d } | |}|jjd d k(r6t||||||| \}}|jsI|durEt|||| | ||}n3d}|d+k(r| ds|jd./t|||| | | ||\}}|j||0y)2Nr'r+T)no_logr*r)r6r() triggeredrr)requiredchoices api_versionstrv1v2)typedefaultrSr9r: componentcustom_detailsdict)rXrAzCreated via Ansible)rYincident_classrFlink_url link_textsourceseveritycritical)rbwarningerrorr1)rYrSrr)r6r*) argument_spec required_ifrequired_one_ofsupports_check_mode)summaryr` timestamprarZclassr[hreftextz^"service_key" is obsolete parameter and will be removed. Please, use "integration_key" insteadrJ acknowledgeresolvez5"service" is a required variable for v2 api endpoint.r)resultchanged)rr\r.rr now isoformatwarnr3 check_moderCr!rN exit_json)r&r'r)r*r6r+r(r9r:rArrGrMstate_event_dictr7outrqs r2mainrzBs   % !- v  D)  'P  %d|L 6 v f  V, 34  6 U+! "V# $f% &6' (",T) 2D<"; < n~&6 7 j>"2 3 << ? FD == D""<0Jmm''(9:O--##M2Kmm *G MM  g &E ]]  x (F""<0J ==  V $D==$$^4L--##H-\\^--/MM%%j1]]&&{3""#34 --++,<=G D }}$}}((4V ==  [ )!==,,[9DL%  5 % "%(J }}'4/VT5*,g|E W  W_T ,fjBC  "78+<   !X  Y$          W C1r4__main__)NNN) __future__rrrrX __metaclass__ DOCUMENTATIONEXAMPLESr"ansible.module_utils.basicransible.module_utils.urlsr+ansible.module_utils.six.moves.urllib.parserr r r r3rCrNrz__name__rrr4r2rszA@ D LK X 4/WWSWbk%R>B4>B8^2B zFr4