from Sentry
2021-02-08 Sentry Memo
$ npm install --save @sentry/react @sentry/tracingNext, import and initialize the Sentry module as early as possible, before initializing React: ts
import React from "react";
import ReactDOM from "react-dom";
import * as Sentry from "@sentry/react";
import { Integrations } from "@sentry/tracing";
import App from "./App";
Sentry.init({
dsn: "https://*****.ingest.sentry.io/5627136",
integrations: [new Integrations.BrowserTracing()],
// We recommend adjusting this value in production, or using tracesSampler
// for finer control
tracesSampleRate: 1.0,
});
ReactDOM.render(<App />, document.getElementById("root"));
- > The above configuration captures both error and performance data. To reduce the volume of performance data captured, change tracesSampleRate to a value between 0 and 1.
// @ts-ignore
console.log([][0].TalkID);
- 
- 
- I'm on a development server and I get an email saying `New alert from keicho-webclient in production
ts
Sentry.init({ ...
environment: process.env.NODE_ENV,
});
Send additional information
Sentry.setContext("Info", { TalkID: TalkID });Server side
$ pip install --upgrade sentry-sdk
Import and initialize the Sentry SDK early in your application's setup:
python
import sentry_sdk
sentry_sdk.init(
"https://013cb069fe1841fb920fd5d7e369debc@o376998.ingest.sentry.io/5628690",
traces_sample_rate=1.0
)
python
@app.route('/')
def root():
1 / 0
return "OK"
I want to make an error on my local server to see if reporting to Sentry is working, but in Flask's development mode, the error is caught and I get a debug screen.
Remove FLASK_ENV=development once
Conversely, with this on, errors are not reported on the local server, which is usually a good thing.
Send additional information
sentry_sdk.set_context("info", {"talk": talk, "text": text})This page is auto-translated from [/nishio/Sentry Memo](https://scrapbox.io/nishio/Sentry Memo) using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.