You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The MuleSoft Analytics Event API, which is crucial for the Axway Amplify agents to integrate MuleSoft AnyPoint platform with Axway Amplify Marketplace and Central, is returning a 410 Gone status code. This indicates that the API has been deprecated and is no longer available, despite the official End of Life date being set for November 30, 2024
To Reproduce
Steps to reproduce the behavior:
Configure the Axway Amplify agent for MuleSoft as per the repository instructions
Attempt to integrate MuleSoft APIs with Axway Amplify Marketplace or Central
Observe the 410 Gone response when the agent tries to access the MuleSoft Analytics Event API
Expected behavior
The Axway Amplify agent should be able to successfully call the MuleSoft Analytics Event API and receive a 200 OK response with the requested analytics data. The API should return data as described in the MuleSoft documentation, including fields such as Application Name, Client IP, Resource Path, and other relevant analytics information.
Logs
{"error":"[Error Code 3005] - could not make request to Mulesoft: 410 - ","level":"error","message":"failed to get analytics data","time":"2024-10-11T16:11:13Z"}
{"level":"debug","timestamp":"2024-10-11T16:11:13.411Z","logger":"apic-agents-trace","caller":"log/logger.go:235","message":"request succeeded","received(bytes)":"37","url":"https://anypoint.mulesoft.com/analytics/1.0/0c9f68c0-2143-49ac-960b-4cd5eb9f6b4c/environments/981534c8-4d8a-4d69-939b-2f638917e8a0/events?endDate=2024-10-11T16%3A11%3A11.786087743Z&fields=Application+Name.Application.Browser.City.Client+IP.Continent.Country.Hardware+Platform.Message+ID.OS+Family.OS+Major+Version.OS+Minor+Version.OS+Version.Postal+Code.Request+Outcome.Request+Size.Resource+Path.Response+Size.Response+Time.Status+Code.Timezone.User+Agent+Name.User+Agent+Version.Verb.Violated+Policy+Name&format=json&startDate=2024-10-11T16%3A10%3A02.481688489Z","duration(ms)":"1625","package":"sdk.api","id":"23a41580-0e20-4698-aac4-0b035f7690a2","method":"GET","status":"410","component":"httpClient"}
{"level":"error","timestamp":"2024-10-11T16:11:13.411Z","caller":"log/logger.go:255","message":"[Error Code 1601] - Error in interval job 121997e2-6863-4ebe-a9c9-5f4ad40cc5f1 execution: [Error Code 3005] - could not make request to Mulesoft: 410 - ","job-name":"interval","package":"sdk.jobs","component":"baseJob","job-id":"121997e2-6863-4ebe-a9c9-5f4ad40cc5f1"}
{"level":"debug","timestamp":"2024-10-11T16:11:13.411Z","logger":"apic-agents","caller":"log/logger.go:205","message":"Job failed, stop all jobs","component":"Pool","package":"sdk.jobs","job-name":"interval","failed-job":"121997e2-6863-4ebe-a9c9-5f4ad40cc5f1"}
{"level":"debug","timestamp":"2024-10-11T16:11:13.411Z","logger":"apic-agents","caller":"log/logger.go:205","message":"Stopping all cron jobs","component":"Pool","package":"sdk.jobs"}
{"level":"debug","timestamp":"2024-10-11T16:11:13.411Z","logger":"apic-agents-trace","caller":"log/logger.go:235","message":"stopping job","component":"Pool","package":"sdk.jobs","job-name":"Traceability Health Check"}
{"level":"debug","timestamp":"2024-10-11T16:11:13.412Z","logger":"apic-agents","caller":"log/logger.go:125","message":"Stopping interval ","component":"baseJob","package":"sdk.jobs","job-name":"Traceability Health Check","job-id":"80bc59c5-ea23-4f89-a7e3-4f9a7842fb63"}
{"level":"debug","timestamp":"2024-10-11T16:11:13.412Z","logger":"apic-agents-trace","caller":"log/logger.go:165","message":"writing to Traceability Health Check stop channel","job-id":"80bc59c5-ea23-4f89-a7e3-4f9a7842fb63","component":"baseJob","package":"sdk.jobs","job-name":"Traceability Health Check"}
{"level":"debug","timestamp":"2024-10-11T16:11:13.412Z","logger":"apic-agents-trace","caller":"log/logger.go:165","message":"wrote to Traceability Health Check stop channel","component":"baseJob","package":"sdk.jobs","job-name":"Traceability Health Check","job-id":"80bc59c5-ea23-4f89-a7e3-4f9a7842fb63"}
{"level":"debug","timestamp":"2024-10-11T16:11:13.412Z","logger":"apic-agents-trace","caller":"log/logger.go:165","message":"finished stopping job","package":"sdk.jobs","job-name":"Traceability Health Check","component":"Pool"}
Environment:
OS: Linux
Agent Version: v1.2.4
MuleSoft AnyPoint Platform Version: Trial Env
Additional context
The premature deprecation of this API before the announced End of Life date requires immediate attention as it breaks the integration between MuleSoft and Axway platforms, potentially affecting customers who rely on this integration for their API management and marketplace strategies.
The text was updated successfully, but these errors were encountered:
Describe the bug
The MuleSoft Analytics Event API, which is crucial for the Axway Amplify agents to integrate MuleSoft AnyPoint platform with Axway Amplify Marketplace and Central, is returning a 410 Gone status code. This indicates that the API has been deprecated and is no longer available, despite the official End of Life date being set for November 30, 2024
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Axway Amplify agent should be able to successfully call the MuleSoft Analytics Event API and receive a 200 OK response with the requested analytics data. The API should return data as described in the MuleSoft documentation, including fields such as Application Name, Client IP, Resource Path, and other relevant analytics information.
Logs
Environment:
Additional context
The premature deprecation of this API before the announced End of Life date requires immediate attention as it breaks the integration between MuleSoft and Axway platforms, potentially affecting customers who rely on this integration for their API management and marketplace strategies.
The text was updated successfully, but these errors were encountered: