Issue Summary

Bitbucket’s log analyzer is presenting a misleading message about a “startup failure” when scanning logs that contain a runtime java.net.UnknownHostException

Steps to Reproduce

1. Configure Bitbucket Data Center / Server with a webhook targeting a host that Is deprecated/non-existent, or has a DNS name that cannot be resolved by the Bitbucket host.
2. Trigger repository/project events that cause Bitbucket to send webhooks to that URL.
3. Check the Bitbucket application logs and confirm entries like: java.net.UnknownHostException: <old-jenkins-host>
4. Allow the Bitbucket log analyser to scan the logs.
5. View the log scan notification and its suggested KB.

Expected Results

• When `java.net.UnknownHostException` occurs at runtime (e.g., webhooks, outbound integrations), the log analyzer should not imply a Bitbucket startup failure.
• Instead, it should show much more accurate KB related to “Bitbucket encountered a `java.net.UnknownHostException` when connecting to an external host.” that focuses on runtime external connectivity / DNS issues, or clearly distinguish between startup-context errors and runtime-context errors before choosing the KB or wording to show.

Actual Results

• The log analyzer flags the `java.net.UnknownHostException` and links to “Bitbucket Server fails to start up with java.net.UnknownHostException exception”
• The customer sees wording implying a startup failure, even though Bitbucket started successfully and is healthy.
• The exception is thrown during normal runtime when sending webhooks to an unreachable external host.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available