APM | AEM Permission Management is an AEM based tool | Content Management System library

AddDefaultIdentity is meant for a web app and not a console App. It adds UI, token providers, and configures authentication to use identity cookies.

For console apps, you can use AddIdentityCore instead.

To me, it looks like span and transaction names are missing (I only see HTTP GET instead of a name)

No, they are not missing. The reason you are seeing name as HTTP GET is due to preference for less cardinal names and the semantic conventions for tracing data. There is a detailed explanation about the naming conventions for the HTTP spans here https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#name. Any data generated by auto-instrumentation libraries will adhere to the semantic conventions specification. I am guessing the visualisation from the linked vendor is coming from manual instrumentation where you as an end user can give any name (although it is recommended everyone uses less cardinal values but there is not enforcement there). I don't think there is anything you can "fix" here.

When the solver fails to find a solution and reports "Solution Not Found", there is a troubleshooting method to diagnose the problem. The first thing to do is to look at the solver output with m.solve(disp=True). The solver may have identified either an infeasible problem or it reached the maximum number of iterations without converging to a solution. In your case, it identified the problem as infeasible.

Infeasible Problem

If the solver failed because of infeasible equations then it found that the combination of variables and equations is not solvable. You can try to relax the variable bounds or identify which equation is infeasible with the infeasibilities.txt file in the run directory. Retrieve the infeasibilities.txt file from the local run directory that you can view with m.open_folder() when m=GEKKO(remote=False).

Maximum Iteration Limit

If the solver reached the default iteration limit (m.options.MAX_ITER=250) then you can either try to increase this limit or else try the strategies below.

• Try a different solver by setting m.options.SOLVER=1 for APOPT, m.options.SOLVER=2 for BPOPT, m.options.SOLVER=3 for IPOPT, or m.options.SOLVER=0 to try all the available solvers.
• Find a feasible solution first by solving a square problem where the number of variables is equal to the number of equations. Gekko a couple options to help with this including m.options.COLDSTART=1 (sets STATUS=0 for all FVs and MVs) or m.options.COLDSTART=2 (sets STATUS=0 and performs block diagonal triangular decomposition to find possible infeasible equations).
• Once a feasible solution is found, try optimizing with this solution as the initial guess.

There is no application listening on port 4200 for your IPv4 address 127.0.0.1. 127.0.0.1 is the IPv4 loopback address. When k6 makes a request to localhost, this hostname resolves to the IPv4 127.0.0.1.

However, your application seems to be listening on port 4200 for your IPv6 address ::1. ::1 is the IPv6 loopback address. curl resolves the hostname localhost to its IPv6 address.

How are you binding your application to the port? Usually, when binding to all interfaces of a host, you'd use the special IP address 0.0.0.0.

I see a potential solutions:

• Make your application bind to IPv4 and IPv6, usually done by binding to address 0.0.0.0.
• Change your k6 script to connect to IPv6 ::1 directly
• Specify --dns "policy=preferIPv6" or add dns:{policy:"preferIPv6"} to your options (since 0.29.0)
• Disable IPv6 in your OS. This is a drastic change and I wouldn't recommend it
• Change your hosts file to resolve localhost to the IPv4 address

One way to locate the error is to open the run directory and inspect the text model file gk_model0.apm.

Posting this as answer out of comments.

Initial ingress rule passes the same path /apm to the APM service, which is confirmed by error in APM pod's logs - "message":"404 page not found","url.original":"/apm"

To fix it, nginx ingress has rewrite annotation. The way it works is described in the link with example.

Final ingress.yaml should look like:

Avoid using a global context, rather create one at the entrypoint and then just pass it as an argument to any function that needs it.

You can make use of the nrgin package provided by the Gin framework.

And in the main() function

• Create an instance of newrelic - newrelic.NewApplication(cfg)
• Call the - nrgin.Middleware(app) function passing in the newrelic instance. This will add the Gin transaction context key - newRelicTransaction to the context.
• Register the function in step 2 as a middleware for all your routes - router.Use(nrgin.Middleware(app))

You can then pass this same context object to your other functions that can accept a parameter of type context.Context since gin.Context is simply implementing the context interface of Go.

Example code

The APOPT solver fails to find a solution. Switching to IPOPT with m.options.SOLVER=3 produces an error:

All gekko problems as defined as static equations and then compiled and sent to a solver. It appears that the definition of the equations changes each time the function is called. The solution is to either use a solver such as Scipy.optimize.minimize as shown here or else use Gekko functions to build the model. Scipy.optimize.minimize is a nonlinear programming solver so the solution may include fractional hands. Here is an example of a mixed integer solution with Gekko.