You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See our project board to track this initiative across all SDKs
Description
This project is to track that each SDK which can support, and has reasonable demand for Cron Monitors at Sentry, has initial support.
Client Reports
We've recently added support for client reports for Crons using the monitor data category. Adding support to all of our SDKs would be helpful to troubleshoot customers if their check-ins are getting discarded for some reason (network issues, rate limits, etc). The envelope item type for monitor check-ins is check_in and the data category for client reports should be monitor.
Thresholds in Monitor Config (Failure & Recovery)
We've just added two additional fields to Relay (getsentry/relay#2842) allowing customers to provide the following properties in their monitor config:
failure_issue_threshold: how many consecutive failures we should wait for to create an issue
recovery_threshold: how many consecutive failures we should keep track to resolve an issue
This is a especially helpful feature for orgs that have lots of monitors and want to configure their monitors programmatically.
Attachments
In Q1, we are planning on implementing the ability to attach files to a check-in and potentially context as well. On attachments, it's likely we'll update the attachment envelope to support a check-in ID or a new envelope dedicated for check-in attachments. We'll discuss with ingest and update with requirements here. The idea is to enable customers to attach log files and other relevant metadata for each job run.
Implementation Overview
The content you are editing has changed. Please copy your edits and refresh the page.
Project Board
See our project board to track this initiative across all SDKs
Description
This project is to track that each SDK which can support, and has reasonable demand for Cron Monitors at Sentry, has initial support.
Client Reports
We've recently added support for client reports for Crons using the monitor data category. Adding support to all of our SDKs would be helpful to troubleshoot customers if their check-ins are getting discarded for some reason (network issues, rate limits, etc). The envelope item type for monitor check-ins is
check_in
and the data category for client reports should bemonitor
.Thresholds in Monitor Config (Failure & Recovery)
We've just added two additional fields to Relay (getsentry/relay#2842) allowing customers to provide the following properties in their monitor config:
This is a especially helpful feature for orgs that have lots of monitors and want to configure their monitors programmatically.
Attachments
In Q1, we are planning on implementing the ability to attach files to a check-in and potentially context as well. On attachments, it's likely we'll update the attachment envelope to support a check-in ID or a new envelope dedicated for check-in attachments. We'll discuss with ingest and update with requirements here. The idea is to enable customers to attach log files and other relevant metadata for each job run.
Implementation Overview
Tasks
SDK Overview
Support for Cron Monitoring
Thresholds in Monitor Config
Node SDK
Python SDK
PHP SDK
failure_issue_threshold
&recovery_threshold
to MonitorConfig sentry-php#1685failure_issue_threshold
&recovery_threshold
sentry-laravel#838Laravel SDK
failure_issue_threshold
&recovery_threshold
sentry-laravel#838Symfony SDK
Ruby SDK
Java SDK
.NET SDK
Go SDK
Elixir SDK
Sentry CLI
The text was updated successfully, but these errors were encountered: