Logo of AppSignal

Menu

Launching JavaScript Error Tracking v1.0.

Appsignal AppSignal on

Good news, everyone! 🎉

Today, we’re proud to announce the launch of our fully-fledged JavaScript error tracking for your front-end applications. From today, you’ll have even more complete insights into your Ruby and Elixir apps — your back-end errors, performance metrics, host metrics, custom metrics and your front-end errors can now all come together under a single interface.

All the tooling you have set up in AppSignal will also work for JavaScript errors. You can set up alerts in Slack, PagerDuty, email or any of our other supported integrations. Find out in which deploy an error first happened, configure triggers for Anomaly Detection, or send front-end errors to your issue tracker of choice.

Errors appear in the frontend namespace, right along with the other namespaces for your Ruby and Elixir apps.

Breadcrumbs

Front-end errors can be quirky. Getting as much context on what happened as possible is helpful in debugging. This is why we built breadcrumbs, where you can track events in your user’s browser leading up to the exception.

Area charts

Try it with your favorite framework

We built our JavaScript error tracking and have been using it ourselves on AppSignal.com for a few months already. We think you’ll love it!

If you use a supported front-end framework, we have integrations for those too:

Getting it running

Install the npm package, and with just a little configuration, you’re good to go! All you need to get started is your Front-end error monitoring key. Find your API key in the “Push and deploy” section of your App settings page, and install the integration.

We’re looking forward to hearing your feedback, and are standing by to help you when needed. Shibboleet by default, as always.

10 latest articles

Go back
Javascript sorcery icon

Subscribe to

JavaScript Sorcery

A true sorcerer combines ancient wisdom and new discoveries. We'll provide you with both. Sign up for our JavaScript Sorcery email series and receive deep insights about JavaScript, error tracking and other developments.

We'd like to set cookies, read why.