PagerDuty Elixir v0.0.1 PagerDuty.Integration
An integration is an endpoint (like Nagios, email, or an API call) that generates events, which are normalized and de-duplicated by PagerDuty to create incidents.
Integrations feed events into services and provide event management functionality such as filtering and de-duplication.
Attributes
@id: id@summary: A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical toname, though it is not intended to be an identifier.@type:@self: the API show URL at which the object is accessible@html_url: a URL at which the entity is uniquely displayed in the Web app@type: valid options are:aws_cloudwatch_inbound_integrationaws_cloudwatch_inbound_integration_referencecloudkick_inbound_integrationcloudkick_inbound_integration_referenceevent_transformer_api_inbound_integrationevent_transformer_api_inbound_integration_referencegeneric_email_inbound_integrationgeneric_email_inbound_integration_referencegeneric_events_api_inbound_integrationgeneric_events_api_inbound_integration_referencekeynote_inbound_integrationkeynote_inbound_integration_referencenagios_inbound_integrationnagios_inbound_integration_referencepingdom_inbound_integrationpingdom_inbound_integration_referencesql_monitor_inbound_integrationsql_monitor_inbound_integration_reference
@name: The name of this integration.@service: The PagerDuty service that the integration belongs to.@created_at: The date/time when this integration was created.@vendor: The vendor that this integration integrates with, if applicable. This can only be set on creation