Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Workspace Instana
Categories Java
Created by Guest
Created on Aug 18, 2023

Retention of JVM data after change in PID/ID

When an Application release, update/change, or outage occurs, all JVM data for the process ID running prior is lost in Instana. This has been confirmed as correct functionality within Instana through ticket "TS013919515"

"It is expected behaviour for JVM. Process restart leads to a new process with a different process ID which is a new entity in our point of view." there for the data that existed for that JVM before the change is gone.

This data should still be available in some way, ideally within the same perspective rather than nothing, when looking at the JVM metrics in the application perspective. This data is used to assist with diagnosing problems or assisting with health and performance issues, service improvements.

Please refer to ticket for screenshots and discussion with Miljan.

Regards,
Application Management.


Idea priority Low
  • Guest
    Reply
    |
    Mar 28, 2024

    Hi,

    In IBM Case TS013317047 "Instana: Technology metrics (JVM, WebSphere, Apache..) not displayed for period before process restart because of different snapshoot IDs" we mentioned same problem. Basically, every time we restart application, webserver or other servis we can't see history metrics on graph for that application/webspere/other because they have different PIDs (or snapshoot ID in instana which is in url).


    I hope that this will be implemented soon.


    Best regards,

    ldrascic

  • Admin
    Joshua Lee
    Reply
    |
    Sep 19, 2023

    Thank you for your submission. We agree that this would be a useful feature. There are some complexities around how we could determine that an entity is the "same" entity as another in the different types of environments (e.g. a JVM managed with systemd vs one in a K8s pod). We are considering how we could do this in a way that would be most seamless for users.

2 MERGED

Aggregate stats for different processes where the INSTANA_SERVICE_NAME environment variable is the same

Merged
Currently, if a process, like a JVM, is restarted, then all of the metrics from the new PID is not associated with the metrics from the old PID. They are treated as completely separate entities. This makes tracking long term metrics (such as Heap ...
5 months ago in Instana / Metric Store 0 Planned for future release