Cloud Management and AIOps

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:

Post your ideas

Start by posting 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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):

  • Cloud Pak for Multicloud Management

  • Cloud Pak for Network Automation - incl Orchestration and Performance Management

  • Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio

  • Control Desk

  • Edge Application Manager

  • IBM Observability with Instana

  • ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8

  • Workload Automation - incl Workload Scheduler

  • Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)

  • Tivoli Application Dependency Discovery Manager - TADDM

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Submitted
Created by Guest
Created on Sep 1, 2021

SSM Process agent logging for the consecutive same action

We are using netcool-ssm-4.0.1. In the PROCESS subagent we observed the following logging pattern.

2021-07-01 06:37:20: prochandle is build 778 (Jan 24 2020)

2021-07-01 06:37:20: Loaded subagent prochandle

2021-07-01 06:37:20: Could not open script file "agent.state"

2021-07-01 06:37:20: Agent running - 30 subagents active

2021-07-01 06:38:10: [PROCESS] Executing 'sh /root/p1.sh' for process row 2

2021-07-01 06:42:50: Repeated 28 times: [PROCESS] Executing 'sh /root/p1.sh' for process row 2

2021-07-01 06:42:50: [PROCESS] Executing 'sh /root/p2.sh' for process row 3

Here, we are monitoring two processes p1 and p2 for their availability. If any of these processes gets killed ssm will bring them up.

Steps followed:

1. We killed the process p1 and ssm brought it up and we see it logged it in ssmagent.log immediately

2021-07-01 06:38:10: [PROCESS] Executing 'sh /root/p1.sh' for process row 2

2. We again killed the p1 and we observed that ssm brought the process up but it did not log the event. We killed p1 multiple times consecutively and every time it brought the process up but it did not log the event in ssmagent.log

3. We then killed p2 and ssm brought up p2. Now we see the logs for p2 as well as for the earlier p1 event

2021-07-01 06:42:50: Repeated 28 times: [PROCESS] Executing 'sh /root/p1.sh' for process row 2

2021-07-01 06:42:50: [PROCESS] Executing 'sh /root/p2.sh' for process row 3

Concern:

In the above log you can see at 06:42:50 it logs the cumulative count(Repeated 28 times) for p1. That means between 06:38:10 and 06:42:50, p1.sh restarted 28 times and ssm logged only once.

Here we would like to make it log ([PROCESS] Executing 'sh /root/p1.sh' for process row 2) 28 times (whenever the event occurs) instead of one single cumulative log line.


Idea Priority High
  • Guest
    Sep 1, 2021

    We have raised this issue to support team and they have asked us to create it as an RFE.

    Please refer case No TS006034976 for more information