Could not parse pager duty event template unexpected field – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch’s Watcher feature is unable to parse the PagerDuty event template due to an unexpected field. This could be due to a typo, incorrect field name, or a field that doesn’t exist in the template. To resolve this issue, you should first verify the field names in your template. Ensure they match exactly with the expected field names. If the field names are correct, check the data type of the fields. They should match the expected data types. Lastly, ensure that the template is correctly formatted and doesn’t contain any syntax errors.

This guide will help you check for common problems that cause the log ” could not parse pager duty event template. unexpected field [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, template.

Log Context

Log “could not parse pager duty event template. unexpected field [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 contexts = list.toArray(new IncidentEventContext.Template[list.size()]);
 } else {
 throw new ElasticsearchParseException("could not parse pager duty event template. unexpected field [{}]";
 return new Template(description; eventType; incidentKey; client; clientUrl; account; attachPayload; contexts; proxy);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?