Skip to Main Content
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
  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 Submitted
Created by Guest
Created on Sep 10, 2025

RBA plug-in doesn't have feature to detect white-spaces and handle appropriately in the json data provided as input to the RBA Action. When the Json is very large, the jq -r based extraction fails to detect whitespaces in json



One of the Action in Runbook which gets the Incident Json as an input parameter was failing with string length parsing issue while we were doing below to extract the  sys_id from Incident JSON.

echo $Commandout_2 | jq | grep -i http| grep -i sys_id  | grep -oP 'sys_id=[^&]*' | cut -d= -f2 | sed 's/[",]//g'

Not sure why the attached Incident JSON is so long with only one Alert being part of it.

Also, I addressed the length issue by writing the json to a file and reading it to parse through jq and fetch the sys_id.

Before: 
output=$(echo $Commandout_2 | jq | grep -i http | grep -i sys_id  | grep -oP 'sys_id=[^&]*' | cut -d= -f2 | sed 's/[",]//g')

After:
file="/tmp/Action`openssl rand -hex 10`"
cat <<EOF > $file
$Commandout_2 
EOF

output=$(cat $file | jq | grep -i http | grep -i sys_id  | grep -oP 'sys_id=[^&]*' | cut -d= -f2 | sed 's/[",]//g')

However, the issue currently is that this new version of the Action is working while running manually but not working as part of the action despite the same version of action is being used and with same parameters. I even retried after publishing the incident.

Attached all the required screeshosts, incident json(Command_out2), Entire Code block:

#echo $Commandout_2 | jq | grep -i http | grep -i sys_id  | grep -oP 'sys_id=[^&]*' | cut -d= -f2 | sed 's/[",]//g'

#echo "1"

file="/tmp/Action`openssl rand -hex 10`"
cat <<EOF > $file
$Commandout_2 
EOF

#echo "2"
#exec 3> /tmp/file
#printf "%s" "$output" >&3
#exec 3>&-

output=$(cat $file | jq | grep -i http | grep -i sys_id  | grep -oP 'sys_id=[^&]*' | cut -d= -f2 | sed 's/[",]//g')
#echo "3"

#output=$(echo $Commandout_2 | jq | grep -i http | grep -i sys_id  | grep -oP 'sys_id=[^&]*' | cut -d= -f2 | sed 's/[",]//g')

if [[ -z "$output" ]]; then
   echo "Error: SysID not found" >&2
   exit 1
else
   echo $output
fi

Let me know if we can do a call on this.

Idea priority High