Sentry¶

You can define a predefined Sentry DSN for your components to use during runtime to report to your Sentry project.

It's also possible for MACH to manage the keys (and DSN values) for you. This allows you to generate a unique DSN per component as well as have fine-grained control over rate-limiting.

To let MACH manage your DSN values, you need to define a auth token, project and organization.

Create auth token¶

Create a new internal integration and choose Project: Admin as permissions.
The rest can be left empty.

Azure connection step 2

Configure MACH¶

Use that token to configure your MACH environment:

---
general_config:
  environment: test
  cloud: aws
  sentry:
    auth_token: <auth-token>
    organization: companyA
    project: mach-services
    rate_limit_window: 21600
    rate_limit_count: 100
  ...

The rate limits can also be defined/overwritten on site and component level

Expose DSN to components¶

MACH needs to know what components want to use the Sentry DSN.
For this you need to include sentry to the list of integrations.
When doing so, MACH expects the component to have one variable sentry_dsn defined (more info)

If the integration is set, MACH will;

Generate a new DSN for the component
Assign the DSN to the sentry_dsn variable