Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

RemoteDependency ResultCode always set to 0 under Spring Boot 4

Open
#4,621 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java, spring-boot

Research direction

Start with the reproduction example and instructions in ApplicationInsights-Java-Repros#18, then trace how Spring Boot 4 remote dependency calls populate ResultCode in Agent 3.7.7. Done means the reproduced RemoteDependency telemetry reports the remote call's correct result code instead of 0 while Success remains true.

Written by the indexing model from the issue text.

Description

Expected behavior

The ResultCode is populated with the correct value from the remote dependency call.

Actual behavior

The ResultCode is always 0. Note that Success is true. It used to be set before we upgraded to Spring Boot 4.

To Reproduce

This issue only started happening after the upgrade to Spring Boot 4.

Please see https://github.com/microsoft/ApplicationInsights-Java-Repros/pull/18 for an example and instructions to reproduce.

With console debug on I can see

{"ver":1,"name":"RemoteDependency","time":"2026-02-13T15:01:15.496Z",...,"resultCode":"0","data":"http://localhost:8080/rest-greeting","type":"Http","target":"localhost:8080","success":true,"properties":{"_MS.ProcessedByMetricExtractors":"True"}}}}

appearing in the logs.

System information

Please provide the following information:

  • SDK Version: Agent 3.7.7
  • OS type and version: MacOS, JDK 21 / 25
  • Application Server type and version (if applicable): Spring Boot 4
  • Using spring-boot? yes
  • Additional relevant libraries (with version, if applicable):
Image
Dominant language
Java
Stars
327
Forks
222
Avg merge
22h 34m
Merged PRs (30d)
14

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/ApplicationInsights-Java

All issues in microsoft/ApplicationInsights-Java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.