Outgoing requests made by Jira Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Jira Data Center comes bundled with a variety of tools designed to support and extend the functionality of your instance.
This article aims to outline the outgoing requests made by these apps, as these are not explicitly documented.
The requests outlined here are based on Jira Data Center versions 9.x, 10.x, and 11.x.
Solution
Identify outgoing requests on your instance
You can identify and analyse outgoing connections made through a forward proxy or debug outgoing connections.
Outgoing requests from bundled apps
App | Functionality | URL |
|---|---|---|
Atlassian Troubleshooting And Support Tools (ATST) | Static Log Analyzer. Its main function is to scan uploaded log files, using regular expressions to match log entries against known issues documented in Atlassian's bug trackers and knowledge base articles. When a match was found, Hercules would suggest relevant articles or bug reports to help diagnose and resolve the issue more quickly. |
|
Pre-upgrade planning Process designed to help administrators determine if your Atlassian application is ready to upgrade to a new version. This feature is typically found in the "Plan your upgrade" section on the Applications page within the product. It checks your current environment against the requirements of the target version, helping to reduce upgrade-related support tickets and improve the overall upgrade experience. |
| |
Security Vulnerability Health Check Checks if your Atlassian product instance is running a version affected by any known critical security vulnerabilities (CVEs). When a vulnerability is detected, admins are notified via a pop-up in the product UI and can click through for more details and remediation steps. |
| |
dc-diagnostics-pipe (Optimization) -
|
| |
Atlassian Notifications (IPN) | Message fetch Jira sends requests to |
|
Atlassian Diagnostics (IPD) | Mail server connection IPDJob to check the connection to incoming/outgoing mail servers by directly pinging them. | Depends on the external mail server configuration. |
External user directories connectivity IPDJob that checks latency to external user directories. | Depends on the external user directory configuration |
Related Information:
Was this helpful?