AWS CloudWatch Error 500 Internal server error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2024 04:02 AM
Hi all
I'm wondering if some of you are also experiencing Error 500 (Internal Server Error) in your AWS CloudWatch, when integrating with ServiceNow Event Management. I have feeling it could be one of two things, perhaps the payload is too big (exceeding the 4k limit for the Event Additional Information field, for example. Or that the JSON is not formatted properly. But how can I get get this confirmed? Have you had similiar issues and how did you solve it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2024 04:17 AM
Hi @MortenPettersen,
The AWS CloudWatch logs must has some more details about this 500 error, did you check that any luck there.
-Thanks,
AshishKM
Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2024 12:56 AM
There's an extra challenge here in that I don't manage or have access to the AWS Account myself. I believe I would benefit from enabling more logging on ServiceNow side as well, for the "sn_em_connector" API. Do you know if there are any properties for enabling this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2024 12:30 PM
The answer that @StephenM provides in this other community post was what I needed:
troubleshooting em/inbound_event webhook - Page 2 - ServiceNow Community