Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

SPIKE: provide support a third-party error logging service

Description

It would be helpful if we could capture additional JS error information with a service like Rollbar, Loggly, Sentry, etc. These services work by embedding a snippet of JS code in the application template.

We would only want to include the snippet in the build given a flag to the CLI, or the presence of a key in the stripes.config.js file.

Spike objectives

  • Evaluate 3 error logging service providers

Spike outcome

  • Select a third-party error logging service based on evaluation

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Khalilah Gambrell February 8, 2021 at 2:46 PM

, can you link the related tickets to this one?

Anton Emelianov February 8, 2021 at 2:42 PM

I see similar ticket floating for other teams. Should we bring it up at the Tech Leads meeting to eliminate redundancy and agreed on the common approach?

Zak Burke February 2, 2021 at 3:06 AM

and provide the opportunity for this by publishing ERROR events that interested modules may [subscribe to in the usual way|STCOR-240].

It is up to the listening modules to interface with the logging service of their choice (e.g. sentry, rollbar, bugsnag).Such modules may also take advantage of STRWEB-2 to provide errorLogging config values at build time, like this:

Khalilah Gambrell December 16, 2020 at 7:02 PM

Need more details

  • What third party error logging services are being used by libraries and hosting providers?

  • Consider errors to support depending on cost structure.

Victoria_Smelova November 18, 2020 at 3:26 PM


It's a new area for Firebird, so might be less effort-consuming for someone working with stripes-sli.
Adding to Firebird backlog for now and we''ll look into it if/when capacity allows.
Feel free to take it back to Stripes Force if they want to work on it earlier than its started by Firebird.

Won't Do

Details

Assignee

Reporter

Labels

Priority

Story Points

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 7, 2019 at 5:42 PM
Updated February 8, 2021 at 2:46 PM
Resolved February 2, 2021 at 3:06 AM
TestRail: Cases
TestRail: Runs