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
I have deployed Pinpoint 3.0.1 using Docker Compose and am currently monitoring our application. However, in the URL Statistic section, the Path values are all being recorded as /NULL.
I have checked and modified the Pinpoint Agent configuration, but the issue persists.
Interestingly, in the Server Map, the URLs appear correctly, but in the URL Statistics, they are recorded as /NULL.
Setup & Tests:
Architecture:Client -> Web (Apache) -> WAS (WildFly with Pinpoint Agent)
Tested scenarios:
Servlet-based endpoints ✅
Spring MVC-based endpoints ✅
AJP worker-based requests ✅
Proxy-based requests ✅
Regardless of the request method, the URL Statistic Path still records /NULL, even though the URLs appear correctly in the Server Map.
Has anyone encountered this issue before, or is there a known solution?
Thanks in advance for your help!
The text was updated successfully, but these errors were encountered:
@emeroad Thank you for your answer, but I already did the way you said it but still get it as NULL.
Also, it's offering multiple services with multiple server, and it doesn't use a unified URL format. Is there a way to get the URL normally?
Subject: Pinpoint 3.0.1 - URL Statistic Path Showing
/NULL
Hello,
I have deployed Pinpoint 3.0.1 using Docker Compose and am currently monitoring our application. However, in the URL Statistic section, the Path values are all being recorded as
/NULL
.I have checked and modified the Pinpoint Agent configuration, but the issue persists.
Interestingly, in the Server Map, the URLs appear correctly, but in the URL Statistics, they are recorded as
/NULL
.Setup & Tests:
Client -> Web (Apache) -> WAS (WildFly with Pinpoint Agent)
Regardless of the request method, the URL Statistic Path still records
/NULL
, even though the URLs appear correctly in the Server Map.Has anyone encountered this issue before, or is there a known solution?
Thanks in advance for your help!
The text was updated successfully, but these errors were encountered: