-
Notifications
You must be signed in to change notification settings - Fork 325
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
Added support for setting destination.address/port on JMS (client) spans who use ActiveMQ Artemis as underlying technology #1905
Conversation
…ans who use ActiveMQ Artemis as underlying technology (elastic#1904)
I don't think this litte enhancement is worth an entry in supported-technologies.asciidoc |
❕ Build Aborted
Expand to view the summary
Build stats
Trends 🧪Steps errorsExpand to view the steps failures
|
Thanks a lot for your awesome contributions @tobiasstadler !! |
(didn't mean to close - wrong button 🤦 ) |
@eyalkoren Personally, I prefer having this in tree. But I am also fine with me maintaining this as an external plugin, if you prefer that. |
BTW. Do you already know when 1.25.0 will be released? |
Why? What's the benefit for you? I'm interested because we want to make our external-plugin contribution experience at least as easy to use/maintain, so any feedback that can help us improve would be great
We do prefer that in this case. Note that these external plugins can still be publicly available to anyone interested and we highly encourage that.
Not yet, not this week, but hopefully in the next week or two. Thanks again for your awesome contributions and feedback! |
The are two reasons why I prefer having it in tree:
|
Ok, I will create an external plugin. |
In case you are not familiar with it already, check out our external plugin example, it does show how to use our tests utilities. In this plugin module there is an example for a unit test, and if you go one level up you can see how we do an integration test for this demo plugin. Worth noticing: the external plugin mechanism is still experimental, so things may change. However, the intention is that any external plugin you develop now will continue working with future releases, even if we change the API or move to a different approach. |
The external plugin uses apm-agent-core as a test dependency. As apm-agent-core is not on maven central (at least I didn't find it there) I have to build it manually first (with the right version) before I can build the plugin. This makes it kinda hard to use CI. |
It can still be developed within your fork of the Java agent. |
FYI: You can find the external plugin here: https://github.com/tobiasstadler/apm-activemq-artemis-destination-plugin |
Good catch, I wasn't aware of that. Sounds like we should publish it by removing this line: apm-agent-java/apm-agent-core/pom.xml Line 21 in ba97d16
|
Although publishing apm-agent-core would solve my problem, I don't know if it is a good idea to do so (from your perspective ). Publishing apm-agent-core also means "exposing" the internal implementation to plugin developers. At the moment I am using an apm-server that is mocked by mock-server (similar to your integration-tests) to capture and validate the created transactions, spans and errors. |
What does this PR do?
Fixes #1904
Checklist