11/02/2022 - Subscription ZenPack Release: Incident Management Integration Service v3.3.1

Services paid subscription ZenPack.zenoss.IncidentManagement

Version 3.3.1 of the Incident Management integration zenpack has been released. This release is compatible with Zenoss versions  6.x and Zenoss Cloud, and has the following additional requirements.

  • Zenoss >= 6.4.1 or later and Zenoss Cloud 
  • ZenPacks.zenoss.PS.QFramework >= 1.2.0

The following changes have been made since the previous release: 3.3.0

Hotfix 3.3.1

  • Bug Fixes
    • SVC-3383: Ensure zenincidentpoll checks the status of all incidents
    • SVC-3381: ensure trigger info is available for clears as well
    • SVC-3382: do not refresh clear from zep if not updating events with notificastion info
    • SVC-3382: remove extra zep refresh when not updating events

Release 3.3.0

  • Bug Fixes
    • SVC-2643: batch requests for zenincidentpoll for ServiceNow
    • SVC-2643: Chunk requests in case we have too many incidents
    • SVC-2837: add default values for Headers and Data fields in HTTP Notification, which includes setting user-agent
    • SVC-3032: Changed closeCode field to configurable instead of hard code value
    • SVC-3032: Added 'timeout' field to request, implemented handlers for different errors
    • SVC-3032: made 'timeout' field provided by default visible
    • SVC-3032: HTTP Notification Timeout made configurable
    • SVC-3034: Remove cz0 prepend within fieldmapping context for smarViewUrl
    • SVC-3320: check impactEvents exist before processing
    • SVC-3319: dont update event if send_initial_occurence is false
    • SVC-3323: update main documentation
    • SVC-3323: formatting fixes to SNow docs
    • SVC-2661: Change impact related event info from score to confidence rating to match data visible in UI
  • Features
    • SVC-2660: Added additional fields for Impact events in order to be more user-readable.
    • SVC-2660: Added getImpactDetails method in order to get correct Impact event details for each event.
    • SVC-2660: added caching in order to prevent multiple calls of DB
    • SVC-3121: Add detail fields for trigger and notification name, and populate when creating incident
    • SVC-3122: triggerName and notificationName fieldmap for UI generated Incidents
    • SVC-3122: add notification and trigger name to fieldmap using notification attributes
    • SVC-3122: Unit test for Tal Context
    • SVC-3122: use notification and trigger object in getTalcontext
    • SVC-3122: add signal attributes for jira context test
    • SVC-3319: Make updating events optional for IntegratorAction
    • SVC-3323: update to use QFramework retry counter abstraction
    • SVC-3323: rework HTTP notification and retry mechanisms; update docs
    • SVC-3323: cleanup separation between Notification Action and Incident Integrate

Release 3.2.4

  • Bug Fixes
    • Moved retry flow for HTTP notification actions to QFramework

Release 3.2.3

  • Bug Fixes
    • Fixes HTTP notification won't send non-initial occurrences

Release 3.2.2

  • Bug Fixes
    • Fixes tracebacks due to missing OAuth settings on non-supported integrations (problem introduced in 3.2.0)

Release 3.2.1

  • Bug Fixes
    • Fixes an extra argument to a method call when processing HTTP Notifications, leading to tracebacks (problem introduced in 3.2.0)

Release 3.2.0

  • Features
    • ServiceNow log response details if hitting the REST API RateLimit
    • Enable OAuth authentication for ServiceNow Import Set and Certified integrations.
    • Added 'jsonstring' context for use in fieldMapping configurations

Release 3.1.1

  • Bug Fixes
    • Allow ServiceNow Certified Notifications stateField to be customized.

Release 3.1.0


  • Added new contexts available in the fieldMapping configuration (defaultFields, mappingUtils,removeField)

   Bug Fixes

  • Prevent an event loop when processing errors if “Send only on initial occurrence” not selected
  • Don’t add multiple zenactiond.conf config files 

Detailed information on this ZenPack is available from the ZenPack Catalog.  

Was this article helpful?
0 out of 0 found this helpful


Powered by Zendesk