sandesvitor commented on issue #6055:
URL:
https://github.com/apache/incubator-devlake/issues/6055#issuecomment-1715777995
Hey @Startrekzky! Thanks for the reply =)
So, actually, I have 2 questions xD
1. Using PagerDuty as a reference, I understand that its API has an
"assignments" key in the response body containing the reference for
"assignee.id" and "assignee.summary":
```json
(...)
"assignments": [
{
"at": "2023-09-06T13:23:05Z",
"assignee": {
"id": "P1THAEX",
"type": "user_reference",
"summary": "Vitor Sandes",
"self": "https://api.pagerduty.com/users/P1THAEX";,
"html_url": "https://example.pagerduty.com/users/P1THAEX";
}
}
],
(...)
```
In Opsgenie, the incident API contains the "responder" key:
```json
(...)
"responders": [
{
"type": "team",
"id": "c0259fb8-2068-48c5-ae09-1b116e3579b1"
},
{
"type": "user",
"id": "b3948a43-fee8-4adc-b7bd-3ac58919f4eb"
}
],
(...)
```
My question is if it's mandatory to use Id and Name for the
ticket.IssueAssignee, such as:
```go
issueAssignee := &ticket.IssueAssignee{
IssueId: domainIssue.Id,
AssigneeId: domainIssue.AssigneeId,
AssigneeName: domainIssue.AssigneeName,
}
```
2. My other question is that Opsgenie has a different approach to Incidents
than PagerDuty. In PagerDuty, an Incident is one or more events (same or
different alert triggers from monitoring tools), which generate an action in
the notification pipe (Service/Escalation/Schedule/User). Opsgenie Incident is
a dedicated object for an operational incident and can be related to a service
and/or stakeholders (PD does not have a similar object, I think). Opsgenie also
has an "Alert" entity that works in a similar way as PagerDuty Incidents.
I tried to collect "alert" metrics, but Opsgenie API has some limitations,
such as:
- To collect the incident-id associated with that alert, you have to GET a
specific alert (this information does not exist in the get alerts list API).
- This is also true for alert description.
Another issue that I couldn't resolve was how to separate these two
entities. If I send them to the board_issues table, they will be considered as
the same. I could create another column named "type" in each model (type =
alert and type = incident), but I don't think it's the most elegant solution
hehe
---
That is it, sorry for the long comment =)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
