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

Application insight profiler is not triggering for memory. No JFR report has been seen for memory.

Open
#3,100 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
observability

Research direction

Start by reproducing the issue with SDK version 3.4.12 on Linux with Spring Boot, using an example in the ApplicationInsights-Java-Repros repository. Enable SDK logs and inspect whether reaching the memory threshold produces a JFR report; done means a memory-triggered JFR report is generated and the reproducer and relevant logs are available.

Written by the indexing model from the issue text.

Description

Needs: Triage :mag:
Expected behavior

The profiler should trigger when the memory threshold is achieved and jfr report should be generated for memory.

Actual behavior

No JFR report is generated for memory.

To Reproduce

Submitting a PR with an example reproducing the issue in this repository would make it easier for the Application Insight maintainers to help you. Before doing this, you have to fork this repository.

System information

Please provide the following information:

  • SDK Version: 3.4.12
  • OS type and version: linux
  • Application Server type and version (if applicable):
  • Using spring-boot? yes
  • Additional relevant libraries (with version, if applicable):
Logs

Turn on SDK logs and attach/paste them to the issue. If using an application server, also attach any relevant server logs.

Be sure to remove any private information from the logs before posting!

Screenshots

If applicable, add screenshots to help explain your problem.
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.