-
-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oban Cron: provide a way to set owner of monitor #824
Comments
@Miradorn this is not part of the SDK payload protocol, so we cannot assign owners from the SDK. I will transfer this to the product repo as a feature request. |
Routing to @getsentry/product-owners-crons for triage ⏲️ |
Assigning to @getsentry/support for routing ⏲️ |
@getsentry/product-owners-crons we cannot assign owners to crons programmatically from the SDK but transferring to your team on other ways to make this workflow better. |
Oh damnit, I'm an idiot and opened it in the wrong repo, wanted to put it into the elixir client library. Sorry, will reopen there! |
@Miradorn you did open it in the elixir library, I moved it here because we cannot do what you asked for from the SDK. |
oh, sorry my bad. |
oh.. well then my bad :) |
@sl0thentr0py yep, I have some time later today. |
Hi there and thanks for the great library!
I'm wondering wether it would be possible to provide a way to set the
owner
of a cron monitor via the automatic integration?We have a setup where we know the owning Sentry team in our codebase and if we could somehow tell the integration to set it correctly it would ease our debugging flow a lot.
e.g. by specifying a callback or some kind of mapping. You probably know best how to achieve it!
Thanks ❤
The text was updated successfully, but these errors were encountered: