SAP-samples / SAP-samples/btp-developer-guide-cap
Set Up Data Collection for SAP Cloud ALM in a CAP Application: Installation of @sap/fesr-to-otel-js fails as it is not read from the private SAP repository
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 97
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Hello SAP BTP CAP Developer Guide Team,
from the page [OpenTelemetry@SAP](https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/data-collection-infrastructure.html?anchorId=section_415688568) I was pointed to Enable Data Collection for Real User Monitoring and Health Monitoring. I did the setup as described for the Repository-Based Shipment Channel.
npm install @opentelemetry/api @opentelemetry/exporter-logs-otlp-grpc @sap/fesr-to-otel-js @sap/xotel-agent-ext-js cf-nodejs-logging-support hdb
It shows error
npm error code E404 npm error 404 Not Found - GET https://registry.npmjs.com/@sap%2ffesr-to-otel-js - Not found npm error 404 npm error 404 '@sap/fesr-to-otel-js@*' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git ur
I updated the package.json with :
"@sap/xotel-agent-ext-js": "https://73555000100200018064.npmsrv.cdn.repositories.cloud.sap/@sap/xotel-agent-ext-js/-/xotel-agent-ext-js-1.5.22.tgz", "@sap/fesr-to-otel-js": "https://73555000100200018064.npmsrv.cdn.repositories.cloud.sap/@sap/fesr-to-otel-js/-/fesr-to-otel-js-1.5.13.tgz"
but now resolving dependencies, it show error:
`npm error code E401
npm error Unable to authenticate, need: BASIC realm="Sonatype Nexus Repository Manager"
npm error A complete log of this run can be found in: /home/user/.npm/_logs/2026-02-24T19_36_21_574Z-debug-0.log`
Need help in resolving this Sonatype Nexus repository manager error.
Thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with documentation/observability/enable-sap-cloud-alm.md and reproduce the listed npm install command for the Repository-Based Shipment Channel. Review the package URLs and authentication failure described in the issue; done means the documented setup installs successfully or clearly explains the required private-repository access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cloud, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100