NodeJS and Attachment

[ErcinDedeoglu]

Maybe it's not a bug, but I'm not sure. because there is no documentation for it.

We are trying to send an attachment of the issue to the sentry via the NodeJS backend application. I wrote the code below by commenting out the API, but it didn't work.

const sentryResponse = Sentry.captureException(err.original);
const client = Sentry.getCurrentHub().getClient();
const { host, path, projectId, port, protocol, user } = client.getDsn();
const endpoint = ${protocol}://${host}${port !== '' ? :${port}: ''}${ path !== '' ?/${path} : '' }/api/${projectId}/events/${sentryResponse}/attachments/?sentry_key=${user}&sentry_version=7&sentry_client=custom-javascript;

fetch(endpoint, {
  method: 'POST',
  body: {
    'variables.file': fs.createReadStream('./README.md')
  },
}).catch((ex) => {
  // we have to catch this otherwise it throws an infinite loop in Sentry
  console.error(ex);
});

} catch (ex) {
console.error(ex);
}

There has to be a simpler way to do this?

[AbhiPrasad]

Hey thanks for writing in! There is currently no first class support for attachments in the JavaScript SDK, but we are working on implementing it soon.

For now, you can attach attachments in beforeSend (grabbing the event id that way). If it's still not working - could you provide a minimal reproduction of your set up + sentry config? That will help us debug.

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[kldavis4]

Example: https://github.com/kldavis4/sentry_nodejs_attachments_example

[yousefa00]

Any idea why this might not be working for me? I have the following Sentry configuration:

const attachmentUrlFromDsn = (dsn: DsnComponents, eventId: string) => {
  const { host, path, projectId, port, protocol, user } = dsn
  return `${protocol}://${host}${port !== '' ? `:${port}` : ''}${
    path !== '' ? `/${path}` : ''
  }/api/${projectId}/events/${eventId}/attachments/?sentry_key=${user}&sentry_version=7&sentry_client=custom-javascript`
}

export const attachAsJson = async (
  attachments: string[],
  event: Sentry.Event,
  client: any
) => {
  const dsn = client?.getDsn()

  if (!dsn || !event.event_id) {
    return
  }

  const endpoint = attachmentUrlFromDsn(dsn, event.event_id)
  logger.info(endpoint)

  const formData = new FormData()
  for (const attachment of attachments) {
    formData.append('attachments', attachment)
  }
  logger.info(formData)

  try {
    await axios.request({
      method: 'POST',
      url: endpoint,
      data: formData,
      headers: {
        'Content-Type': `multipart/form-data; boundary=${formData.getBoundary()}`
      }
    })
    return event
  } catch (err) {
    logger.error(err)
    return null
  }
}

And include this where the attachment is in scope:

Sentry.addGlobalEventProcessor(async event => {
    try {
      const client = Sentry.getCurrentHub().getClient()
      if (!client) {
        return null
      }
      await attachAsJson([attachment], event, client)
    } catch (ex) {
      logger.error(ex)
    }
    return event
  })

I see the Sentry events created correctly, and logging the API request status code is 201, yet there are no attachments on the actual event created. Any help would be greatly appreciated.

[pkaminski]

I have a similar problem to @yousefa00. I adapted @kldavis4's code above and get a 201 Created when uploading the attachment, but nothing shows up in Sentry on the attachments tab. One difference is that I grab the event ID from the return value of Sentry.captureException rather than in beforeSend or an event processor, but I don't imagine that ought to matter.

Can any from Sentry speculate on what might be going wrong given that no errors pop up at any point during the process? If it helps trace things, one such recent event was 4ec36c5f7ed14ca69ea40d9c50487390. Thanks!