Go to content

Monitoring Errors and Slowdowns with a JS Frontend and Node Backend - Chris Stavitsky, Node Congress

Node Congress 2022 #NodeCongress #Node #GitNation Website – https://nodecongress.com/ Follow the link to watch the full version of all the conference talks, QnA’s with speakers and hands-on workshop recordings β†’ https://portal.gitnation.org/events/node-congress-2022 Talk: Monitoring Errors and Slowdowns with a JS Frontend and Node Backend We've got a JavaScript frontend hitting a Node (Express.js) backend. We'll go through how to know which party is responsible for which error, what the impact is, and all the context needed to solve it. This event would not take place without the support of sponsors: πŸ† Platinum Sponsors Prisma β†’ https://www.prisma.io/ Toptal β†’ https://www.toptal.com/ πŸ₯‡ Gold Sponsors StackHawk β†’ https://www.stackhawk.com/ Sentry β†’ https://sentry.io/ DNSimple β†’ https://dnsimple.com/ Platform.sh β†’ https://platform.sh/ MUX β†’ https://mux.com/ πŸ₯ˆ Silver Sponsors Stream β†’ https://getstream.io/ Twilio β†’ https://www.twilio.com/ MediaJAMS β†’ https://mediajams.dev/ PolyScale β†’ https://www.polyscale.ai/ Turing β†’ https://developers.turing.com/ Fauna β†’ https://fauna.com/ Adevinta β†’ https://www.adevinta.com/careers Microsoft β†’ https://www.microsoft.com/en-ie/

February 17, 2022