Sentry 10 / Jira server integration - alert rule / base url questions

Hi there. I’m working on setting up integrations in Sentry 10, and Jira is the current one. We run both Sentry and Jira on premises.

We have a service mesh / reverse proxy layer, and the hostname we access websites from is not the same as the hostname that a server accesses another server from. I was able to work around this by editing the setup dialog’s redirect URL after getting redirected, but when linking an issue the incorrect hostname is used (since it’s the only one Sentry knows about). Is there a way I can provide a separate base URL for “urls being clicked in the browser”, while retaining the existing hostname for making API calls from the server? (Even hand-editing the database would be fine)

Secondly: I am currently able to link and create new issues, but I am not seeing Jira show up in the alert rule target drop-down. I’m not sure why not or how to troubleshoot it. Any guidance?

Don’t know why you need such an interesting setup but I think system.url-prefix is the setting you are looking for: https://develop.sentry.dev/config/#general

There’s also system.internal-url-prefix which is used by Relay etc to communicate with Sentry through the private internal network: onpremise/config.example.yml at 7365a034575b3beeb6fc70103f13916b52b7f29a · getsentry/onpremise · GitHub

Not sure if this is supported, especially on Sentry 10. Are you able to upgrade to a newer version as v10 is quite old and there were a bunch of additions and fixes since then (including Jira integrations).

Don’t know why you need such an interesting setup

Security constraints are managed differently for machine<->machine than human<->machine

Are you able to upgrade to a newer version[…]?

10 is the latest version, yeah? Although, I know Sentry has moved to a date-based versioning thing now. We’re specifically using 21.02.0 at the moment – but have been referring to the current version as “10” since the last major release is “9”

internal-url-prefix seems like it might do what I want, I’ll give it a try

Ah, right. internal-url-prefix won’t help since I’m talking about a split in hostnames for Jira, not for Sentry. But it might solve a different problem we were having.