Skip to content

Feature Request: Extend Sentry Provider to Support Custom Integration Settings #595

Open
@V-Legendre

Description

@V-Legendre

Summary:

We would like to request an extension to the Sentry provider to support custom settings for various Sentry integrations. Currently, the provider does not cover all use cases for configuring Sentry actions, and additional flexibility is needed to accommodate different integration requirements.

Background:

The existing Sentry provider has limited support for configuring Sentry actions with custom settings. This limitation hinders the ability to fully utilize Sentry's integration capabilities with third-party services. For example, users may need to set specific parameters for creating tickets, sending notifications, or triggering workflows in external systems.

Use Case:

We need the ability to configure Sentry actions with custom settings for various integrations. This could include settings for creating tickets in issue tracking systems (e.g., Jira, Linear, GitHub Issues).

Example Configuration:

{
    "id": "sentry.rules.actions.notify_event_sentry_app.NotifyEventSentryAppAction",
    "sentryAppInstallationUuid": "example-uuid",
    "settings": [
        {"name": "customSetting1", "value": "value1"},
        {"name": "customSetting2", "value": "value2"},
        {"name": "customSetting3", "value": "value3"}
    ]
}

Request:

We kindly request the maintainers to consider extending the provider to support custom settings for Sentry integrations. This would involve:

  • Adding a flexible mechanism to define and pass custom settings to Sentry actions.
  • Implementing the logic to handle these settings when creating or updating resources.
  • Providing documentation and examples on how to use these custom settings for different integrations.

Thank you for considering this feature request!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions