[source-zendesk-support] Missing property sla in schema ticket_metric_events

[emiel-signpost]

Connector Name

source-zendesk-support

Connector Version

4.0.1

What step the error happened?

None

Relevant information

The source-zendesk-support connector is missing some properties for the schema ticket_metric_events.
We are currently working on reporting SLAs and there is an extra property called sla for apply_sla events in that schema that contains important information. Example (source):

{ 
     "id": 123457,  
     "ticket_id": 987, 
     "metric": "requester_wait_time",  
     "instance_id": 1, 
     "type": "apply_sla", 
     "time": "2015-08-27T08:00:00Z",  
     "sla": {
         "target": 60,    
         "business_hours": true,    
         "policy": {
             "id": 531,
             "title": "Main Policy",    
             "description": "Measure all tickets"   
         }  
     }
 }

This one is the most import for us now, but there are a few additional properties that I also don't see in the ticket_metric_events.json from the connector. These are the additional properties mentioned in the API Reference:

Name	Type	Read-only	Mandatory	Comment
sla	object	yes	no	Available if type is "apply_sla". The SLA policy and target being enforced on the ticket and metric in question, if any.
group_sla	object	yes	no	Available if type is "apply_group_sla". The Group SLA policy and target being enforced on the ticket and metric in question, if any.
status	object	yes	no	Available if type is "update_status". Minutes since the metric has been open.
deleted	object	yes	no	Available if type is "breach". In general, you can ignore any breach event when deleted is true.

I haven't looked in the connector code too much but I assume the fix is relatively easy by adding the properties to the ticket_metric_events.json?

References:

• Ticket Metric Events API Reference
• Ticket Metric Event Types Reference

Relevant log output

No response

Contribute

• Yes, I want to contribute

[bodschut]

Having the same issue here, these optional fields in the response payload of the metric events are crucial for some usecases...

[yashupadhyaya25]

How can i contribute to this issue ??

[daniellomartra]

+1 to this. FYI the data is already in airbyte's internal tables, just needs to be added to final tables.