Uptime Alert Configuration
Learn more about the options for configuring an uptime alert.
Sentry Uptime Monitoring is currently in open beta, so be gentle - features are still in-progress and may have bugs. We recognize the irony. For any questions or feedback, you can reach us on Github Discussions.
Sentry provides several configuration options for creating an uptime alert based on your organization's needs as explained below.
First, specify which environment this alert rule belongs to. Any uptime issues that will be created from this alert rule will then be set to your specified environment.
You'll notice that the “Environment” dropdown list you see here shows the same environments as the “Environment” dropdown in your project (not including hidden environments).
Specify which project your alert rule belongs to so that any uptime issues you create will show up for that specific project.
Configure how Sentry should execute an HTTP uptime check, by specifying:
- URL: The URL for which Sentry should execute an uptime check request.
- Method: The request method used to execute the uptime check. Available options are
GET
,POST
,HEAD
,PUT
,DELETE
,PATCH
, andOPTIONS
. - Headers: The request headers included in the uptime check request.
- Body: The body message to include in the uptime check request. (This is only available when the method is set to
POST
,PUT
, andPATCH
.)
Make sure to include a Content-Type
header in your headers configuration in case the specified URL requires it. For example, a JSON message body would have a Content-Type
header of application/json
.
If the specified URL is behind a firewall, make sure Sentry's Uptime Bot can execute requests to it. Learn more.
Give your alert a descriptive name, for example, "Landing Page" or "Contact Page".
Lastly, choose a team to associate with your alert so that members of that team are able to edit the alert if they want to. Note, that you can only add teams that you're a member of. If no team is assigned, anyone will be able to edit the alert.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").