Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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 ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Submitted
Workspace Planning Analytics
Created by Guest
Created on Aug 10, 2026

Add Logger Name Filter to Planning Analytics Server Logs

Dear team,


Current Behavior

The Planning Analytics Server Logs interface currently allows filtering by Log Level and time range, but does not provide a filter for Logger Name.

Log entries already contain Logger Name information, for example:

  • TM1.API

  • TM1.Cube

  • TM1.Process

  • TM1.MDX

  • TM1.Client

  • TM1.HttpSession

When troubleshooting a specific component, administrators must manually search through large volumes of unrelated log entries.

Requested Enhancement

Add a Logger Name filter to the Server Logs interface.

The filter should:

  • Allow users to select one or multiple Logger Names

  • Be combinable with existing filters such as Log Level and time range

Example:

Logger Name = TM1.Process
Log Level = ERROR

→ Shows only process-related error messages.

Benefit

  • Significantly faster and more efficient troubleshooting

  • Especially valuable in large, high-activity Planning Analytics environments

  • Enables administrators to isolate messages from a specific component without manually searching through unrelated entries

  • The Logger Name information is already present in the log data; this enhancement would simply expose it as a usable filter in the UI

Related Idea

This request is related to CPDIDEAS-I-3031 (Server Logs - Increase number of lines to display and download), but addresses a different limitation: the ability to filter log entries by Logger Name.

Thanks in advance.

With best regards,
Vitalij

Needed By Yesterday (Let's go already!)
  • Guest
    Aug 24, 2026

    +1!

    We would strongly support this enhancement.

    The Logger Name is already available as part of the log information, so exposing it as a filter in the PAW Server Logs interface would provide a significant improvement for troubleshooting.

    In larger environments, filtering only by time range and log level can still result in a very large number of unrelated log entries. Being able to select one or multiple Logger Names and combine this with the existing filters would make it much easier to focus on the relevant information.

    For example:

    Logger Name = TM1.API
    Log Level = ERROR
    Time Range = 09:00–09:30

    This would be particularly useful when investigating REST API activity, process execution, locking, memory-related issues, or other specific TM1 components.

    We also see this as complementary to CPDIDEAS-I-3031, which addresses the limitation on the number of log lines that can be displayed and downloaded. Increasing the number of available log entries is important, but being able to efficiently filter those entries by Logger Name is equally important when working with large logs.

    Ideally, the Logger Name filter should be dynamically populated from the available loggers, rather than relying on a fixed list, so that it remains useful as new loggers are introduced in future versions.

    This would be a relatively focused enhancement with a significant practical benefit for administrators and consultants working with Planning Analytics.