Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Thank you for raising this request. We understand the value of improving visibility for enterprise Java applications using JPA with EclipseLink, especially in mission-critical environments where ORM behavior, database access patterns, and caching can materially affect performance.
Today, Instana provides Java/JVM visibility such as process/runtime metrics and supports database visibility through Java database/JDBC instrumentation. This means many underlying database calls made by an EclipseLink-based application may already be visible at the JDBC/database span level, depending on the application and driver setup.
The gap we see in this request is specifically EclipseLink/JPA-level visibility, such as ORM query attribution, EclipseLink cache behavior, or other framework-specific diagnostics beyond generic JDBC spans.
We are not planning dedicated EclipseLink instrumentation in the immediate roadmap at this time. However, we see this as a valid enterprise Java use case and will evaluate it further if we see stronger customer demand or a clearly defined gap that cannot be addressed through existing JDBC/JVM visibility.
If you have any additional feedback or thoughts, or if there is anything else I can do, please do not hesitate to reply to this message to continue the conversation.
Please note: IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion.
Thank you for raising this idea and for sharing your feedback.
Instana currently provides visibility into database interactions through JDBC instrumentation. Since JPA implementations such as EclipseLink ultimately execute database operations through JDBC, these calls should already appear in Instana traces.
are there specific troubleshooting scenarios where the current JDBC-level visibility is not sufficient?