-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multiple service names #136
Comments
Blocked by elastic/apm-server#1175 |
This is not blocked anymore elastic/apm-server#1175 is done. |
Is there an ETA for this? We would appreciate this as it makes our task a lot easier. |
Enables to have multiple service names per JVM, one per class loader. closes elastic#136
@wolframhaussig I'm currently working on this so it won't be too long probably 🙂 I assume you want this so that you can have different service names for different applications deployed to the same application server? The way I have implemented this is that it takes the |
@felixbarny |
Could you specify what you mean by that? Do you mean the Axis2 standalone server?
Are all of these webservices packaged in the same war file? How would you differ between them? Does it contain multiple Axis2 servlets which are mapped to different URLs? Another thing to note here is that general JVM metrics like GC statistics will use the service name configured in |
I meant the Axis2 webApp. Our structure is this:
In the Axis2 webApp there is a directory WEB-INF/services- In this directory are over 60 .aar files. Currently I always see AxisServlet#doPost as name. Of course it would be cool if the apm agent would recognise the service.name from the Axis2 services... |
Would it be an option for you to enable use_path_as_transaction_name so that the transactions have different names? |
That would be fine for me.
So this would currently not work as the Axis2 controller is already recognised, right? |
Hmm, yeah, that's true. Forgot about that. Another approach could be to set the transaction name in a custom servlet filter manually: https://www.elastic.co/guide/en/apm/agent/java/current/public-api.html#api-set-name |
I will leave it for now as I am not happy to modify hundreds of web applications/web services. As a fallback I might reconfigure the apm server to logstash output and do the mapping from url to transaction there. |
Enables to have multiple service names per JVM, one per class loader. closes #136
In application servers, it is possible to deploy multiple applications. Currently, the agent only supports one service name per JVM.
This should add the ability to configure one service name per
javax.servlet.ServletContext#getContextPath
.The text was updated successfully, but these errors were encountered: