Finding out the precise causes of errors in log messages from events forwarded to remotes

Forge Forge Platform and Tools
1

Hi all, I have one app running in Jira that is subscribed to a couple events, all of which sent to a remote endpoint. So I have no code actually running in forge, my app is just a manifest.yml file that hooks up events and remotes.

I set up an alert and have seen a bunch of errors today on the Atlassian side. I could spot none of these errors on my end, and the error log entries are so uninformative that there is no way of knowing why these failed (networking issues, http statuses, timeouts…???) - I would venture that these requests never reached my remote. Is there any way to see that information? How can I get access to useful diagnosis for these calls?

Example log message (what precisely was the problem?).

Failed remote request
{
"remoteUrl": "bot.teamos.is/jira/events"
}
Environment: Production
Invocation ID: ec50c31e-bf96-4258-8f59-9815ef15ed8f
Trace ID: 67e3e59f43ce895e36f1e6ba2c33bfe3
Module: core:endpoint
Function: teamos-bot-events
Version: 3.0.0
Site: (subdomain).atlassian.net
Product: Jira
1 Like
2

Hi Carles,

Can you please raise a request with Support; we can route to the required team that owns this and share more detailed information to further investigate.

Cheers
Ben

3

Thanks Benny, I’ve done so.