Skip to content

Milestones

List view

  • Content Security Policy

    Collection of issues related to improving CSP, HPKP, ExpectCT, and ExpectStaple.

    Due by April 28, 2023
    •5/5 issues closed
    100% complete0 open5 closed

  • Scoped Configuration for Relay

    Sentry has several (nested) scopes: global, organization, project, key. We have multiple instances where we would like to propagate configuration values from a higher scope that can be dynamically changed: - Values of a higher scope (e.g. a global configuration value) are **copied** into every project (key) state. The majority of Relay’s memory usage today is consumed by globally shared values in project states. - Changing a global field involves a lot of time because thousands of project states have to be recomputed. https://www.notion.so/sentry/Global-config-propagation-in-Relays-23f4fb1eeece4e12adf7b9b706cc0949

    No due date
    •1/1 issues closed
    100% complete0 open1 closed

  • Incident

    No due date
    •5/5 issues closed
    100% complete0 open5 closed

  • Maintenance

    No due date
    •30/30 issues closed
    100% complete0 open30 closed

  • Upgrade Tokio in Relay

    Due by April 30, 2023
    •35/35 issues closed
    100% complete0 open35 closed

  • Improve Quality of Transaction Names

    Projects with a high number of different Transaction Names are problematic for our metrics infrastructure (introduced by the Dynamic Sampling initiative), because they generate **high cardinality**. Having unparameterized URLs that are also grouped, but treated as separate transaction names also decreases the **usability and value of the Performance product**. The transaction name is a tag on all extracted Performance metrics, e.g. `transaction.duration` or `measurements.lcp`. The number of transaction names for a project/org can quickly grow when an **identifier** is part of the transaction name. **Goal** We need to provide a reasonable experience out of the box with no additional steps required for the vast majority of customers. This means to provide the full parameterized experience for customers (or as close to full as we can get) on all platforms. Sentry needs to understand which transactions are unparameterized and could be grouped together, in order to display them under one meaningful transaction name for the customer to visualise in the Performance product. **User Story** _“As a user, I want my transactions to be automatically normalised/parameterized, without the need for extensive manual instrumentation on my side, so that I can get started with Performance as quickly as possible and be able to visualise the performance of each of my transactions.”_ **More Resources** https://www.notion.so/sentry/Normalize-Transaction-Names-acab68918db0464fb39e1e57e61851dd

    Due by April 30, 2023
    •4/4 issues closed
    100% complete0 open4 closed