IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
In a high-traffic system it can be difficult to determine which log entries in the seas logs are related to a given authentication attempt. Currently we're forced to grep / search for the specific username /timeframe and then manually parse through the files to try and determine which entries are relevant to the issue we're investigating. It would be helpful if all of the log entries for a given authentication request were flagged with some kind of unique ID to make it easier to find the relevant logs.
How will this idea be used?
User reports some kind of authentication failure. Operations team can look in logs for a single log entry for the authentication attempt and then use the unique ID found in the log entry to locate all other pertinent entries, without manually perusing the file or mistakenly conflating log entries from unrelated authentication attempts.
|What is your industry?||Automotive|
|What is the idea priority?||Medium|
|Link to original RFE|