Skip to content
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

Monitor-open-telemetry-exporter showing errors since it is searching wrong file path for package json #17556

Closed
KarishmaGhiya opened this issue Sep 10, 2021 · 1 comment · Fixed by #17595
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Monitor - Exporter Monitor OpenTelemetry Exporter

Comments

@KarishmaGhiya
Copy link
Member

KarishmaGhiya commented Sep 10, 2021

We are using monitor open telemetry exporter for data ingestion and getting errors related to packageJson path
This is the CI - https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1087949&view=logs&j=e7ca4586-4898-5923-3654-78b12b0c49d3&t=db75396e-40b1-58b4-1714-dc94b07e9427

The following is the stack-trace of the error -

packageJsonPath
'C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\package.json'
packageJsonPathTsNode
'C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\package.json'
(node:22228) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\package.json'
    at Object.openSync (fs.js:476:3)
    at Proxy.readFileSync (fs.js:377:35)
    at Context._loadInternalContext (C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\node_modules\@azure\monitor-opentelemetry-exporter\dist\index.js:1475:49)
    at new Context (C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\node_modules\@azure\monitor-opentelemetry-exporter\dist\index.js:1428:14)
    at getInstance (C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\node_modules\@azure\monitor-opentelemetry-exporter\dist\index.js:1507:20)
    at createTagsFromSpan (C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\node_modules\@azure\monitor-opentelemetry-exporter\dist\index.js:1707:21)
    at readableSpanToEnvelope (C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\node_modules\@azure\monitor-opentelemetry-exporter\dist\index.js:1850:18)
    at C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\node_modules\@azure\monitor-opentelemetry-exporter\dist\index.js:2036:47
    at Array.map (<anonymous>)
    at AzureMonitorTraceExporter.export (C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\node_modules\@azure\monitor-opentelemetry-exporter\dist\index.js:2036:33)
    at C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@opentelemetry\tracing@0.22.0_@opentelemetry+api@1.0.2\node_modules\@opentelemetry\tracing\src\export\BatchSpanProcessorBase.ts:155:30
    at async_hooks.js:313:14
    at AsyncResource.runInAsyncScope (async_hooks.js:197:9)
    at AsyncLocalStorage.run (async_hooks.js:311:35)
    at AsyncLocalStorageContextManager.with (C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@opentelemetry\context-async-hooks@0.22.0_@opentelemetry+api@1.0.2\node_modules\@opentelemetry\context-async-hooks\src\AsyncLocalStorageContextManager.ts:40:36)
    at ContextAPI.with (C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@opentelemetry\api@1.0.2\node_modules\@opentelemetry\api\src\api\context.ts:77:42)
    at C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@opentelemetry\tracing@0.22.0_@opentelemetry+api@1.0.2\node_modules\@opentelemetry\tracing\src\export\BatchSpanProcessorBase.ts:151:19
    at new Promise (<anonymous>)
    at BatchSpanProcessor._flushOneBatch (C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@opentelemetry\tracing@0.22.0_@opentelemetry+api@1.0.2\node_modules\@opentelemetry\tracing\src\export\BatchSpanProcessorBase.ts:145:12)
    at C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@opentelemetry\tracing@0.22.0_@opentelemetry+api@1.0.2\node_modules\@opentelemetry\tracing\src\export\BatchSpanProcessorBase.ts:130:28
    at new Promise (<anonymous>)
    at BatchSpanProcessor._flushAll (C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@opentelemetry\tracing@0.22.0_@opentelemetry+api@1.0.2\node_modules\@opentelemetry\tracing\src\export\BatchSpanProcessorBase.ts:123:12)
    at C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@opentelemetry\tracing@0.22.0_@opentelemetry+api@1.0.2\node_modules\@opentelemetry\tracing\src\export\BatchSpanProcessorBase.ts:94:23
    at async Promise.all (index 0)
(Use `node --trace-warnings ...` to show where the warning was created)
<node_internals>/internal/process/warning.js:43
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 10, 2021
@KarishmaGhiya
Copy link
Member Author

The actual path should be of this value -

PS C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\node_modules\@azure\monitor-opentelemetry-exporter> ls

Directory: C:\code\sdk-for-js\common\temp\node_modules\.pnpm\@azure\monitor-opentelemetry-exporter@1.0.0-beta.4\node_modules\@azure\monitor-opentelemetry-exporter

Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 9/1/2021 3:29 PM dist
d----- 9/1/2021 3:29 PM dist-esm
d----- 9/1/2021 3:29 PM types
-a---- 9/1/2021 3:28 PM 1002 CHANGELOG.md
-a---- 9/1/2021 3:28 PM 4720 package.json
-a---- 9/1/2021 3:28 PM 3659 README.md

@KarishmaGhiya KarishmaGhiya added the Client This issue points to a problem in the data-plane of the library. label Sep 10, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 10, 2021
@KarishmaGhiya KarishmaGhiya added Monitor - Exporter Monitor OpenTelemetry Exporter needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Sep 10, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 10, 2021
@KarishmaGhiya KarishmaGhiya added this to the [2021] October milestone Sep 10, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Monitor - Exporter Monitor OpenTelemetry Exporter
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants