Skip to content

Sentry management in your environment using the Ametnes Platform#

This page explains how to manage an existing Sentry data service in the Ametnes Platform.

Warning

Only one management operation can be performed at a time: General, Upgrading, or Configuration.

General#

Use this section to update the general details of the Sentry resource, such as its name and description.

Upgrading#

  1. Open the Sentry resource in the Ametnes Platform console.
  2. Open Advanced Settings.
  3. Change Service Version to the newer Sentry release you want to run.
  4. Save the resource and wait for the update to complete.

Configuration#

  1. Open the Sentry resource in the Ametnes Platform console.
  2. Open Configuration.
  3. Update the configuration you need.
  4. Save the resource and wait for the update to complete.

Architecture#

Use architecture to change the preset tier size for the Sentry deployment.

Tier Description Use case
Starter Minimal footprint tier for evaluation and lightweight usage. Local testing, demos, proof of concept, tiny internal apps.
Small Entry production tier for low traffic workloads. Small production rollout, single-team app monitoring.
Basic Moderate production baseline with app-tier redundancy. Growing product teams with always-on observability.
Medium Medium-load production with larger data and worker capacity. Multi-service production environments with steady ingest growth.
Large Higher-throughput production with stronger buffering and query capacity. Business-critical workloads and broader org adoption.
XLarge High ingest and query headroom for large product surfaces. Large production deployments with many teams and services.
2XLarge Very high throughput preset for enterprise-scale ingestion. Enterprise-scale production with high cardinality and long retention.
3XLarge Extended scale preset derived from 2XLarge. Very large multi-team environments with heavy query workloads.
4XLarge Top-end preset in this tier set for extreme sustained load. Largest-scale deployments with high ingest and complex analytics.

SMTP#

The smtp field controls email delivery for your Sentry instance. Email is used for user invitations, password resets, scheduled reports, and alerts.

Set the field to one of the following:

Value Effect
(empty) Email is disabled.
ametnes Use the Ametnes-managed relay (recommended). Ametnes provisions a scoped, send-only credential and configures Sentry automatically.
smtp://... or smtps://... Use your own SMTP server or relay. See the connection string reference below.

Connection string reference#

A custom relay is configured with a single connection string:

scheme://[username[:password]@]host[:port][?option=value&...]
Part Meaning
scheme smtp:// enables STARTTLS and defaults to port 587. smtps:// enables implicit TLS/SSL and defaults to port 465.
username[:password] Optional. Omit the whole user:pass@ segment for an unauthenticated relay.
host SMTP server hostname. Required.
port Optional. Only defaults are applied (587/465), so always include the port when your server listens on another one, such as 25.
?tls=off Disables encryption entirely (plaintext). Use this when your server does not support STARTTLS or SSL.
?from= Overrides the From email address, for example ?from=alerts%40example.com.
?fromname= Overrides the From display name, for example ?fromname=Ametnes%20Sentry.

Reserved characters in the username, password, and query option values must be percent-encoded: @ → %40, : → %3A, / → %2F, space → %20.

Choosing the right scheme for your mail server#

Choose the value that matches what your mail server or provider supports:

  • STARTTLS on the submission port (587, recommended for most providers such as SendGrid or Microsoft 365):
smtp://apikey:SG.example_key@smtp.sendgrid.net:587
smtp://user:password@smtp.example.com:587
  • Implicit TLS/SSL (servers that require encryption from the first byte, usually port 465):
smtps://user:password@smtp.example.com:465
  • Plain, unauthenticated relay that does not support STARTTLS (common on port 25, for example an internal mail gateway or smarthost). Encryption must be disabled or delivery fails:
smtp://mail.example.com:25?tls=off
  • Plain relay with authentication:
smtp://user:password@mail.example.com:25?tls=off

STARTTLS must be supported by the server

STARTTLS is an SMTP extension that the server must advertise and support. The smtp:// scheme enables STARTTLS, so it only works against servers that support it. If you use a plaintext-only relay (for example on port 25), smtp://mail.example.com:25 without ?tls=off fails with an error such as STARTTLS extension not supported by server. Append ?tls=off for that use case. Email is then sent unencrypted over the network.

Examples#

# Disable email (leave empty)

# Ametnes-managed relay
ametnes

# SendGrid API key, STARTTLS on port 587
smtp://apikey:SG.example_key@smtp.sendgrid.net:587?from=alerts%40example.com&fromname=Ametnes%20Sentry

# Custom provider, implicit TLS on port 465
smtps://user:password@smtp.example.com:465

# Custom provider, STARTTLS on port 587, unauthenticated
smtp://smtp.example.com:587

# Plain unauthenticated relay on port 25 (no STARTTLS support)
smtp://mail.example.com:25?tls=off

# Plain authenticated relay on port 25
smtp://relayuser:relaypass@mail.example.com:25?tls=off

Troubleshooting#

  • STARTTLS extension not supported by server - your mail server does not support STARTTLS. Use ?tls=off to connect in plaintext, or switch to a server that supports STARTTLS/TLS.
  • Mail accepted but not received - check the recipient's spam folder, and confirm the from address (and fromname) are set to a value your mail server accepts.
  • Plain port 25 delivery fails to connect - many ISPs and cloud providers block outbound port 25. Use the submission port 587 with STARTTLS when your relay supports it.