Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/newrelic-experimental/newrelic-java-sap-bi
Instrumentation for SAP PI/PO Server
https://github.com/newrelic-experimental/newrelic-java-sap-bi
bi data instrumentation java newrelic nrlabs nrlabs-data nrlabs-odp observability-data sap sap-pi sap-po
Last synced: 8 days ago
JSON representation
Instrumentation for SAP PI/PO Server
- Host: GitHub
- URL: https://github.com/newrelic-experimental/newrelic-java-sap-bi
- Owner: newrelic-experimental
- License: apache-2.0
- Created: 2022-08-29T15:41:21.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-12-09T15:48:41.000Z (about 1 month ago)
- Last Synced: 2024-12-09T16:45:42.124Z (about 1 month ago)
- Topics: bi, data, instrumentation, java, newrelic, nrlabs, nrlabs-data, nrlabs-odp, observability-data, sap, sap-pi, sap-po
- Language: Java
- Homepage:
- Size: 45.6 MB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# New Relic Java Instrumentation for SAP
Instrumentation for the SAP framework.
## Agent Configuration
Because of the way JDBC is implemented in SAP and the way that the New Relic Java Agent instruments JDBC, it is necessary to disable the agent instrumentation and use a customized set of instrumentation included with this instrumentation set.
To disable,
1. Edit newrelic.yml
2. Find the following stanza:
3. Add the following lines after the last line
com.newrelic.instrumentation.jdbc-generic:
enabled: false
4. Save newrelic.yml
## JMX Collection
To configure the Java Agent to collect SAP related JMX metrics see: https://github.com/newrelic-experimental/newrelic-java-sap-bi/blob/main/JMX-Configuration.md.
## Installation
To install, follow the instruction in the release notes
## Getting Started
Once installed, the instrumentation will track transactions through the various SAP components.
## Instance Naming
Each instance in an SAP cluster is named according to two SAP environment variables if set. These are SAPSYSTEMNAME and SAPMYNAME. If both are set the instance name is set to ***value of SAPSYSTEMNAME***-***value of SAPMYNAME***. If just SAPMYNAME is set then the instance name is set to ***value of SAPMYNAME***. If neither is set then default instance names are used.
## Logs ##
Serveral of the instrumentation modules can be used to generate logs containing SAP data. This is done because the amount of data sent via custom events is limited. This data can be monitored via the New Relic Logs product.
For details on what is collected and how to configure see https://github.com/newrelic-experimental/newrelic-java-sap-bi/blob/main/Logs/Logging.md
## Custom Events
A number of custom events are generated by this instrumentation package. For details see https://github.com/newrelic-experimental/newrelic-java-sap-bi/blob/main/CustomEvents.md.
## Building
Note that because SAP is a proprietary software it is necessary for you to have access to a licensed instance of SAP. Each component has a file named holder.txt in the lib directory that is a list of necessary jar files. Copy those jars from your instance to the lib directory.
Building the extension requires that Gradle is installed.
To build the extension jars from source, follow these steps:
### Build single extension
To build a single extension with name *extension*, do the following:
1. Set an environment variable *NEW_RELIC_EXTENSIONS_DIR* and set its value to the directory where you want the jar file built.
2. Run the command: ./gradlew *extension*:clean *extension*:install
### Build all extensions
To build all extensions, do the following:
1. Set an environment variable *NEW_RELIC_EXTENSIONS_DIR* and set its value to the directory where you want the jar file built.
2. Run the command: ./gradlew clean install
## 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](https://discuss.newrelic.com) where our community members collaborate on solutions and new ideas.
## Contributing
We encourage your contributions to improve [Project Name]! 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](../../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](https://hackerone.com/newrelic).
## License
[Project Name] is licensed under the [Apache 2.0](http://apache.org/licenses/LICENSE-2.0.txt) License.
>[If applicable: [Project Name] also uses source code from third-party libraries. You can find full details on which libraries are used and the terms under which they are licensed in the third-party notices document.]