Struct pagerduty::integration::AcknowledgeEvent

pub struct AcknowledgeEvent<'a> {
    // some fields omitted
}

Acknowledge events cause the referenced incident to enter the acknowledged state.

While an incident is acknowledged, it won't generate any additional notifications, even if it receives new trigger events. Your monitoring tools should send PagerDuty an acknowledge event when they know someone is presently working on the problem.

Methods

impl<'a> AcknowledgeEvent<'a>

fn new<S>(service_key: S, incident_key: S) -> Self where S: Into<Cow<'a, str>>

Create a new event

• service_key: The GUID of one of your "Events API" services. This is the "service key" listed on a Generic API's service detail page.

• incident_key: Identifies the incident to resolve. This should be the incident_key you received back when the incident was first opened by a trigger event. Resolve events referencing resolved or nonexistent incidents will be discarded.

fn set_details<T: ?Sized>(self, details: &T) -> Self where T: Serialize

Set event details

An arbitrary JSON object containing any data you'd like included in the incident log.

For an example, please see the similar TriggerEvent::set_details.

fn set_description<S>(self, description: S) -> Self where S: Into<Cow<'a, str>>

Set text that will appear in the incident's log associated with this event.

Trait Implementations

impl<'a> Serialize for AcknowledgeEvent<'a>

fn serialize<__S>(&self, serializer: &mut __S) -> Result<(), __S::Error> where __S: Serializer

Derived Implementations

impl<'a> Debug for AcknowledgeEvent<'a>

fn fmt(&self, arg_0: &mut Formatter) -> Result