Sentry Tools
Sentry Create Organization Monitor
Utilisez Sentry Create Organization Monitor avec Sentry Tools via Aident Loadout. Vérifiez les entrées, sorties, la configuration, le tarif et le risque avant exécution.
Action d'écritureNiveau de risque 2 sur 5Connexion par clé API
Description du fournisseur
Creates a new monitor (type 'cron_job') within a Sentry organization to track scheduled tasks, allowing configuration of its name, slug (which must be unique if provided), status, owner, and muting preferences for incidents.
Tarifs et limites
- Tarif
- Action gratuite
- Paiement unifié
- Non pris en charge actuellement
Entrées
- The human-readable name for the monitor. This name is used in notifications and the Sentry UI.namestringObligatoire
- A unique identifier for the monitor within the organization. If not provided, Sentry will generate one. It must match the pattern `^[a-z][a-z0-9_\-]*$`. Changing this slug after creation requires updating any instrumented check-in calls.slugstring
- The Sentry actor ID (team or user) to be designated as the owner of this monitor. Format: 'user:{user_id}' or 'team:{team_id}'. If not provided, the monitor will be unassigned.ownerstring
- The configuration for the monitor including schedule type, schedule, and timing settings. This is a required field.configobjectObligatoire
- The initial status of the monitor. 'active' monitors accept check-ins and contribute to quotas, while 'disabled' monitors do not. Allowed values: 'active', 'disabled'. Note: Monitors are typically created with 'disabled' status by default and must be activated separately.statusstring
- The project slug to associate the monitor to. This is a required field.projectstringObligatoire
- A boolean flag to control incident creation for this monitor. If true, monitor incidents (alerts) will be suppressed. Defaults to false if not provided.is_mutedboolean
- The identifier (ID or slug) of the Sentry organization to which this monitor will belong.organization_id_or_slugstringObligatoire
Sortie observable
- Data from the action executiondataObligatoire
- Error if any occurred during the execution of the actionerrorstring
- Whether or not the action execution was successful or notsuccessfulbooleanObligatoire
Skills qui utilisent cette Action
Cas d’usage associés
Aucun cas d’usage associé et vérifié pour le moment.