> ## Documentation Index
> Fetch the complete documentation index at: https://docs.localops.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Crashes

We don't recommend crashes to be recorded and seen at an environment level as it will be too fragmented for your team to
manage. So you can sign up for a crash reporting service and use it as your central store for recording crashes.

[Sentry](https://sentry.io/welcome/) is the most popular choice today. There are also other prominent tools like
[BugSnag](https://www.bugsnag.com/) which you can explore and decide if they will be a better fit for your team.

You can sign up for an account in one of these services and embed their SDK in Front-end and Back-end codebases to
record crashes. Every unique application you make is usually modeled as a project in these crash reporting tools and
crashes are recorded with environment tag.

For environment tag, you can use name like *production*, *staging*, *customer-1*, *customer-4*, etc., to identify which
environment saw the crash. This tag name can be seen on your Grafana dashboard, which you can use to query the logs.