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 Future consideration
Workspace Instana
Categories Kubernetes
Created by Guest
Created on Jul 18, 2023

Find Kubernetes entities if the end time is greater than the entity lifetime

At the moment one can find an entity (e.g. Kubernetes Deployment) if the start time is earlier than the entity creation time but it is not possible to find an entity if the selected end time in the UI is later than the entity deletion/termination/end time.

E.g. entity existed from ~ 2023-07-14 10:00 to 2023-07-18 10:59

Expected behaviour vs actual:
* Start time 2023-07-01 to 2023-07-15 (start time before entity lifetime starts, end time before lifetime ends) expected: finds entity, actual: finds entity GREAT
* Start time 2023-07-15 to 2023-07-17  (start time after entity lifetime starts, end time before lifetime ends) expected: finds entity, actual: finds entity GREAT
* Start time 2023-07-01 to 2023-07-18 11:00 (start time before entity lifetime starts, end time after lifetime ends) expected: finds entity, actual: does not find entity FAIL
* Start time 2023-07-18 10:00 to 2023-07-18 11:00 (start time after entity lifetime starts, end time after lifetime ends) expected: finds entity, actual: does not find entity FAIL
* Relative time last x minutes / days (start time before or after entity lifetime starts, end time (now) after lifetime ends) expected: finds entity, actual: does not find entity FAIL
 

This results really poor usability as you cannot find your entities in list views (e.g. Kubernetes Deployments) and if you already selected your entity and change the timeframe then the Kubernetes Deployment not found dialog appears which suggests available time ranges (which is good) but it resets your start time and end time which you wanted to focus on which is bad.

Idea priority Low