getsentry / getsentry/sentry

Enhancements to Crons like having metadata, additional statuses, etc...

Open
#54,536 8 comments 0 reactions 0 assignees View on GitHub
Feature Product Area: Crons
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

### Problem Statement

Hi there,

I would like to ask is it possible to allow having custom metadata for Check-ins in Crons like it exists for performance events for example. This would be helpful for us to give more context (information) related to Check-in. If this is not possible can you expend Check-ins with some field like some message or context or description where we will be able to add some more info?

Is it possible add value warning to status field for Check-ins beside having in_progress, ok and error? By doing so we would be able to know that some jobs might need you to pay attention at them, but it is not critical like error.

Is it possible to increase size of environment name to something longer than 64 characters? Asking this, because in some cases we were hitting the limit of 64 characters, since there name we creating by concatenating type of environment (since we don't have metadata or some other field where we can put this) + company name (it can be up to 30 characters) + tenant id (for Azure it is usually 36 characters) in order to be uniquely identify the customer from the environment name.

Thank you in advance!

### Solution Brainstorm

_No response_

### Product Area

Crons

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.