import {Fragment} from 'react'; import ExternalLink from 'sentry/components/links/externalLink'; import {Layout, LayoutProps} from 'sentry/components/onboarding/gettingStartedDoc/layout'; import {ModuleProps} from 'sentry/components/onboarding/gettingStartedDoc/sdkDocumentation'; import {StepType} from 'sentry/components/onboarding/gettingStartedDoc/step'; import {t, tct} from 'sentry/locale'; // Configuration Start export const steps = ({ dsn, }: { dsn?: string; } = {}): LayoutProps['steps'] => [ { type: StepType.INSTALL, description: (

{tct( 'Edit your [mixCode:mix.exs] file to add it as a dependency and add the [sentryCode::sentry] package to your applications:', {sentryCode: , mixCode: } )}

), configurations: [ { language: 'elixir', description:

{tct('Install [code:sentry-sdk]:', {code: })}

, code: ` defp deps do [ # ... {:sentry, "~> 8.0"}, {:jason, "~> 1.1"}, {:hackney, "~> 1.8"}, # if you are using plug_cowboy {:plug_cowboy, "~> 2.3"} ] end `, }, ], }, { type: StepType.CONFIGURE, description: (

{tct( 'Setup the application production environment in your [code:config/prod.exs]', { code: , } )}

), configurations: [ { language: 'elixir', code: ` config :sentry, dsn: "${dsn}", environment_name: :prod, enable_source_code_context: true, root_source_code_path: File.cwd!(), tags: %{ env: "production" }, included_environments: [:prod] `, }, { description: (

{tct( 'The [environmentNameCode:environment_name] and [includedEnvironmentsCode:included_environments] work together to determine if and when Sentry should record exceptions. The [environmentNameCode:environment_name] is the name of the current environment. In the example above, we have explicitly set the environment to [prodCode::prod] which works well if you are inside an environment specific configuration like [configCode:config/prod.exs].', { environmentNameCode: , includedEnvironmentsCode: , prodCode: , configCode: , } )}

{tct( 'An alternative is to use [code:Mix.env] in your general configuration file:', {code: } )}

), configurations: [ { language: 'elixir', code: ` config :sentry, dsn: "${dsn}", included_environments: [:prod], environment_name: Mix.env `, }, ], }, { description: (

{tct( 'This will set the environment name to whatever the current Mix environment atom is, but it will only send events if the current environment is [prodCode::prod], since that is the only entry in the [includedEnvironmentsCode:included_environments] key.', { prodCode: , includedEnvironmentsCode: , } )}

{t( "You can even rely on more custom determinations of the environment name. It's not uncommon for most applications to have a 'staging' environment. In order to handle this without adding an additional Mix environment, you can set an environment variable that determines the release level." )}
), language: 'elixir', code: ` config :sentry, dsn: "${dsn}", included_environments: ~w(production staging), environment_name: System.get_env("RELEASE_LEVEL") || "development" `, }, { description: (

{tct( "In this example, we are getting the environment name from the [code:RELEASE_LEVEL] environment variable. If that variable does not exist, it will default to [code:'development']. Now, on our servers, we can set the environment variable appropriately. On our local development machines, exceptions will never be sent, because the default value is not in the list of [code:included_environments].", { code: , } )}

{tct( 'If using an environment with Plug or Phoenix, add the following to [plugRouterCode:Plug.Router] or [phoenixEndpointCode:Phoenix.Endpoint]:', {plugRouterCode: , phoenixEndpointCode: } )}

), language: 'elixir', code: ` # Phoenix use Sentry.PlugCapture use Phoenix.Endpoint, otp_app: :my_app # ... plug Plug.Parsers, parsers: [:urlencoded, :multipart, :json], pass: ["*/*"], json_decoder: Phoenix.json_library() plug Sentry.PlugContext # Plug use Plug.Router use Sentry.PlugCapture # ... plug Plug.Parsers, parsers: [:urlencoded, :multipart, :json], pass: ["*/*"], json_decoder: Phoenix.json_library() plug Sentry.PlugContext `, additionalInfo: (

{tct( '[sentryPlugContextCode:Sentry.PlugContext] gathers the contextual information for errors, and [sentryPlugCaptureCode:Sentry.PlugCapture] captures and sends any errors that occur in the Plug stack. [sentryPlugContextCode:Sentry.PlugContext] should be below [sentryPlugParsersCode:Plug.Parsers] if you are using it.', { sentryPlugCaptureCode: , sentryPlugContextCode: , sentryPlugParsersCode: , } )}

), }, ], }, { title: t('Capture Crashed Process Exceptions'), description: (

{tct( 'This library comes with an extension to capture all error messages that the Plug handler might not. This is based on [link:Logger.Backend]. You can add it as a backend when your application starts:', { link: ( ), } )}

), configurations: [ { language: 'elixir', code: ` # lib/my_app/application.ex def start(_type, _args) do Logger.add_backend(Sentry.LoggerBackend) `, }, ], }, { title: t('Capturing Errors'), description: ( {t( 'If you use the LoggerBackend and set up the Plug/Phoenix integrations, all errors will bubble up to Sentry.' )}

{t('Otherwise, we provide a simple way to capture exceptions manually:')}

), configurations: [ { language: 'elixir', code: ` try do ThisWillError.really() rescue my_exception -> Sentry.capture_exception(my_exception, [stacktrace: __STACKTRACE__, extra: %{extra: information}]) end `, }, ], }, ]; // Configuration End export function GettingStartedWithElixir({dsn, ...props}: ModuleProps) { return ; } export default GettingStartedWithElixir;