Receiving events from Node.js back-end server hosted elsewhere, but not from AWS Lambda

[hamirmahal]

Is there anything special I should keep in mind when sending events to Mixpanel from AWS Lambda?

Events sent from a very similar Node.js backend hosted elsewhere show up in the dashboard just fine.

I read https://docs.mixpanel.com/docs/tracking-methods/integrations/amazon-s3.

[hamirmahal]

I see

2024-12-14T07:49:21.357Z	5a498e73-d15c-49e9-bfd1-e5d721bbbc9e	DEBUG	Sending the following event to Mixpanel {
  data: {
    event: 'Link Clicked',
    properties: {
      '$os': 'Linux',
      '$browser': 'Chrome',
      mp_lib: 'node',
      '$lib_version': '0.18.0'
    }
  }
}

in the AWS CloudWatch log for the AWS Lambda, but these events don't show up in my Mixpanel dashboard, even after refreshing the dashboard several times and waiting a few minutes.

Another, almost identical Node.js backend server hosted off AWS is able to send Mixpanel events to the same dashboard without issue.

[hamirmahal]

I hosted the Node.js server that's sending events to Mixpanel just fine at https://render.com/.

[hamirmahal]

I updated my code to

  try {
    mixpanel.track("Link Clicked", {
      // isDevelopment: true,
      $os: os.name || "Unknown",
      $browser: browser.name || "Unknown",
    });
  } catch (error) {
    console.error("Error tracking event:", error);
  }

and the AWS CloudWatch logs don't show the catch block occurring.

2024-12-14T21:12:06.250Z
2024-12-14T21:12:06.250Z	06c429f6-6f8b-44c7-bb0a-7cb45ce30a88	DEBUG	Sending the following event to Mixpanel {
  data: {
    event: 'Link Clicked',
    properties: {
      '$os': 'Linux',
      '$browser': 'Chrome',
      mp_lib: 'node',
      '$lib_version': '0.18.0'
    }
  }
}

2024-12-14T21:12:06.729Z
END RequestId: 06c429f6-6f8b-44c7-bb0a-7cb45ce30a88
2024-12-14T21:12:06.729Z
REPORT RequestId: 06c429f6-6f8b-44c7-bb0a-7cb45ce30a88 Duration: 726.27 ms Billed Duration: 727 ms Memory Size: 128 MB Max Memory Used: 84 MB Init Duration: 181.66 ms