newrelic-experimental/newrelic-java-spring-cloud

Instrumentation of Spring Cloud Gateway for use with the New Relic Java Agent

New Relic Java Instrumentation for Spring Cloud Gateway

New Relic Java agent instrumentation extension for Spring Cloud Gateway.

Installation

This use this instrumentation.

1. Download the latest release.
2. In the New Relic Java Agent directory (directory containing newrelic.jar), create a directory named extensions if it doe not already exist.
3. Copy the jars into the extensions directory.

Building

If you make changes to the instrumentation code and need to build the instrumentation jars, follow these steps

1. Set environment variable NEW_RELIC_EXTENSIONS_DIR. Its value should be the directory where you want to build the jars (i.e. the extensions directory of the Java Agent).
2. Build one or all of the jars.
   a. To build one jar, run the command: gradlew moduleName:clean moduleName:install
   b. To build all jars, run the command: gradlew clean install
3. Restart the application

Getting Started

After deployment, you should be able to see parts of your Apache Sling flows showing up in transaction traces.

Support

New Relic has open-sourced this project. This project is provided AS-IS WITHOUT WARRANTY OR DEDICATED SUPPORT. Issues and contributions should be reported to the project here on GitHub.

We encourage you to bring your experiences and questions to the Explorers Hub where our community members collaborate on solutions and new ideas.

Contributing

We encourage your contributions to improve Salesforce Commerce Cloud for New Relic Browser! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project. If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at [email protected].

A note about vulnerabilities

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

License

newrelic-java-spring-cloud-gateway is licensed under the Apache 2.0 License.

newrelic-java-spring-cloud's Issues

External Services Viewing

Right now with the extension in place it shows the Transactions broken down more granularly instead of just /NettyDispatcher which is fantastic.

However, it would be great for the External Services also showed the proper destinations rather than localhost.