Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
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 Submitted
Created by Guest
Created on Oct 30, 2026

Support PII/Sensitive Data Masking for Externally Ingested OTEL Traces

Organizations may ingest OpenTelemetry (OTEL) traces from external applications, services, or third-party systems. When PII masking controls are enabled, sensitive information contained within these externally generated traces is currently not redacted before storage and display.

This creates a gap in privacy and compliance controls, as data masking behavior is not consistently applied across all telemetry sources.

Current Behavior

  • Externally generated OTEL traces are ingested and stored as received.
  • Existing PII masking controls apply to generated content but do not affect externally supplied telemetry payloads.
  • The observability layer does not perform masking or redaction on incoming OTEL trace data.

Expected Behavior

  • PII masking controls should optionally apply to externally ingested OTEL traces before storage and presentation.
  • Administrators should be able to configure masking policies for sensitive information within telemetry payloads.
  • Privacy controls should behave consistently regardless of the source of telemetry data.
Idea priority Urgent