A series of

  • 1 minute Quick use of The latest version of Docker Sentry-CLI – create version
  • Quick use of Docker start Sentry-CLI – 30 seconds start Source Maps
  • Sentry For React
  • Sentry For Vue
  • Sentry-CLI usage details
  • Sentry Web Performance Monitoring – Web Vitals
  • Sentry Web performance monitoring – Metrics
  • Sentry Web Performance Monitoring – Trends
  • Sentry Web Front-end Monitoring – Best Practices (Official Tutorial)
  • Sentry Backend Monitoring – Best Practices (Official Tutorial)
  • Sentry Monitor – Discover Big data query analysis engine
  • Sentry Monitoring – Dashboards Large screen for visualizing data

directory

  • Create an environment
  • Environmental filter
    • Issues
    • Releases
  • Hidden environment

Environment is a Sentry supported tag that you can (and should) add to your SDK. Typically, a tag accepts any value, but it is intended to refer to a naming convention for code deployment, such as development, testing, pre-release, or production.

The environment helps you better filter issues, versions, and user feedback in the Issue Details page of Sentry. IO. On this page, you can view information about a particular environment, with emphasis on the latest releases. If you are using a multi-phase publishing process, you can also select a different default environment and set conditions matching the environment attribute to limit alerts to a particular publishing phase.

Use Project to separate different services or applications, and Environment to separate different environments or release phases in each. If you select one or more projects in the global header of Sentry’s Web UI, the Environment selector displays only the environment associated with the events in the selected project.

Every organisation’s Environments are unique. However, the environment Settings are defined by project, because you can hide the environment for each project.

Create an environment

Sentry automatically creates the environment when it receives an event with the environment tag. The environment is case sensitive. You can also create the environment when you first initialize the SDK, as described in the documentation for each SDK.

  • Docs. Sentry. IO/platforms/j…

Environmental filter

Issues

If an issue contains events from more than one environment, the issue appears when you select any of them. Sentry defines an issue as a group of similar events. If you mark one or more events in an issue with a particular environment, the issue will appear in your view when the issue is filtered by the environment. For example, if an issue consists of an event labeled Production and an event labeled Staging, the issue will appear in your view when filtered by Production and Staging.

In addition, the environment filter affects all metrics associated with the issue, such as the number of users affected, the time series graph, and the number of events.

Releases

Release itself is independent of the environment, but can be deployed to different environments. When you select an environment on the Releases page, it displays releases deployed to that environment. For example, when filtering by QA and Prod, the versions deployed to the QA and Prod environment will appear in your view. All metrics associated with an issue in a given version will be affected by the environment filter. A deploy must have an environment.

For more details on configuring Release and deploy, see the complete documentation on Release.

  • Docs. Sentry. IO/product/rel…

Hidden environment

Since you cannot delete the environment, Sentry can choose to hide it from the UI. Hiding the environment can be useful when you no longer send events from the environment, or when you accidentally create an environment that is no longer needed. You can Hide the environment from the environment drop-down list by navigating to Project Settings > Environments and selecting “Hide”, but events sent to the environment will still count towards your quota.

If a project is hidden, you will not see that environment in the environment selector unless another project with events from the same environment is also selected (and not hidden in its project Settings).