Define ignore_errors & ignore_transactions (#884)

* ignore_errors & ignore_transactions

* Update src/docs/sdk/features.mdx

Co-authored-by: Philipp Hofmann <[email protected]>

* clarify that transaction name should be included

---------

Co-authored-by: Philipp Hofmann <[email protected]>

Author: smeubank

src/docs/sdk/features.mdx

@@ -55,6 +55,12 @@ if random() < sample_rate:
     transport.capture_event(event)
 ```
 
+To further simplfiy ignoring certain events from being sent to sentry, it is also suggested to provide `ignoreTransactions` and `ignoreErrors` (or exception, choose terminology which is best for the platform). The array for `ignoreTransactions` specifically should contain an array of transaction names, as is stored in the transcation event schema (ie `GET /info`). These options should provide a simple way to allow users to discard events (ignore) from before they are sent to sentry. Prevents sending data which is is undesired and may consume quota or resources on the Sentry server.
+
+```python
+ignore_transactions = ['GET /api/health','/api/v1/*']
+```
+
 ## Rate Limiting
 
 Respect Sentry’s HTTP 429 `Retry-After` header, or, if the SDK supports multiple payload types (e.g. errors and transactions), the `X-Sentry-Rate-Limits` header. Outgoing SDK requests should be dropped during the backoff period.