-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle Incident Log Entries of User Notification #201
Conversation
Thanks for submitting this PR! As a rule, we're not adding support for any undocumented API features. And, as of right now, none of these fields are documented in the PagerDuty API Reference. I'm working with the engineering team that owns this endpoint to see if we can change that. Will keep you posted. Until then, the |
Hi @stmcallister ! I'm also interested in retrieving User data from the LogEntries. Has there been any progress getting this added to the library? Or are we still waiting on having the Pagerduty API reference updated before adding this change? |
@joez-tkpd @obl1v1us I'm not a PD employee so I don't have any inside baseball, but it seems like the API documentation still has not been updated to include these fields: This branch is also conflicting with @stmcallister can you speak to the documentation status? |
@joez-tkpd with #264 merged, some of what you're trying to accomplish is now possible. The I'll leave the question about the API documentation for Scott. |
@joez-tkpd I'm thinking of raising a support ticket to PagerDuty to ask about the Do you have an example log entry where the |
Ah I found it. |
Hey everyone! Sorry for taking so long on this one. After trying to get one of the engineering teams to update the PagerDuty API Docs to match this PR I took matters into my own hands and figured out how to do it myself. The PR has been approved and should be merged in the coming days. Thanks for your patience! |
Log Entry Docs are updated. |
@joez-tkpd this will be part of v1.5.0 when released (merged via #377). |
Add
User
struct onLogEntries
Because on Incident's Log Entries
/incidents/{id}/log_entries
when"type": "notify_log_entry"
the payload doesn't contain any information about the notified user except on user object
additionally add
Service
onLogEntries
additionally
Channel
also missedNotification
object