Hello,

Zabbix already has a media type for ServiceNow incidents but not for events.
To give the customers the possibility to use ServiceNow IT Operations Managements (ITOM) capabilities, it is essential that Zabbix sends alerts with informations as events instead of incidents.

This would be possible by sending events to the ServiceNow event endpoint (Preferred way, and suggested by ServiceNow)
[ServiceNow event endpoint doc|
https://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/event-management/task/configure-listener-transform-script.html

Alternative way would be using the Alarm Management Open API from ServiceNow. (Very uncommon)
[Alarm Management Open API|
https://www.servicenow.com/docs/bundle/yokohama-api-reference/page/integrate/inbound-rest/concept/alarm-open-api.html]

Maybe necessary to use additional REST API endpoints from ServiceNow.
[ServiceNow Rest API documentation|
https://www.servicenow.com/docs/bundle/yokohama-api-reference/page/build/applications/concept/api-rest.html]

Key Requirements:

• OAuth authentication
• Create/Update ServiceNow events by Zabbix alerts
• Zabbix Webhook parameters should be used to map additional infos from Zabbix to the ServiceNow event
• Add Zabbix informations as JSON to the "additional_info" ServiceNow field

Benefits created by the feature request:

• Possibility to use the improved Event Correlation from ServiceNow with other sources than Zabbix
• Reducing alert noise and improve root cause analysis in ServiceNow
• ServiceNow can apply event rules, thresholds and maintenance rules, Optimizing the creation and escaltions of incidents inside of ServiceNow
• Better integration to ServiceNow ITOM to allow the usage of features like alert aggregation, impact analysis and automated remediation
• Better scalability for ServiceNow in comparison to creating incidents directly by Zabbix