Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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 Nov 5, 2024

Add missing "Resources for the endpoint URI not found" to server log with call details for REST transformed SOAP API

When a user calls a non-existent method of a REST API, there will be a related log in the server.log at info level that allows administrator to track down the source of the request:

For example:
2024-11-05 15:10:27 HKT [YAI.0101.0018I] (tid=798263) [default][hosta][APIGW:74f3ad2d-2408-4083-8293-2efc510bc033:798263:3985d8fed7ed400aaef114b2776a813f]  Error occurred while processing the request, Error: Resource /healthcheckx not found 
2024-11-05 15:10:27 HKT [YAI.0201.0052T] (tid=798263) [default][hosta][APIGW:74f3ad2d-2408-4083-8293-2efc510bc033:798263:3985d8fed7ed400aaef114b2776a813f]  Session ID: 3985d8fed7ed400aaef114b2776a813f. Setting payload value for the proxy service, test-apiService in the service invocation event.
Payload: [{"Exception":"API Gateway encountered an error. Error Message: Resource /healthcheckx not found. Request Details: Service - test-apiService , Operation - null, Invocation Time:3:10:27 PM, Date:Nov 5, 2024,  Client IP - 192.168.1.1, User - Default and Application:null"}] 

But if a user calls a non-existent method of a REST transformed SOAP API, no log will be visible in the server.log. There will only be a error log with no detail in the error log, which means we are not able to identify who is causing the error or which API was being called.

This discrepancy is causing issue with our production monitoring capability as alerts are triggered by the error log entry, but our monitoring team is not able to find any relevant information to contact the API consumer or API provider regarding these logs. False alarms are generated constantly and clouding our ability to monitor API usage.

Idea priority High