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

[BUG] Azure.Monitor.OpenTelemetry.Exporter 1.0.0-beta.13 creates ReadOnlyDictionary messages #37832

Closed
cataggar opened this issue Jul 25, 2023 · 10 comments
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor - Exporter Monitor OpenTelemetry Exporter needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@cataggar
Copy link
Member

Library name and version

Azure.Monitor.OpenTelemetry.Exporter 1.0.0-beta.13

Describe the bug

When I upgrade from 1.0.0-beta.12 to 1.0.0-beta.13 in this internal PR, a bunch of new traces show up with System.Collections.ObjectModel.ReadOnlyDictionary\u00602[System.String,System.Object] as the message.

In the VS output window while debugging, the json shows:

{"name":"Message","time":"2023-07-25T09:26:22.6228639Z","iKey":"6dd2e7ec-afc5-4231-8bce-075f266bf999","tags":{"ai.cloud.role":"unknown_service:func","ai.cloud.roleInstance":"CPC-catag-TL2L0","ai.internal.sdkVersion":"dotnet6.0.9:otel1.5.0:ext1.0.0-beta.13"},"data":{"baseType":"MessageData","baseData":{"message":"System.Collections.ObjectModel.ReadOnlyDictionary\u00602[System.String,System.Object]","severityLevel":"Information","properties":{"Name":"StartExpireTrials","Count":"1","Timestamp":"7/25/2023 9:25:56 AM \u002B02:00","AvgDurationMs":"00:00:00.5144233","MaxDurationMs":"00:00:00.5144233","MinDurationMs":"00:00:00.5144233","Successes":"1","Failures":"0","SuccessRate":"100"},"ver":2}}}

In the Azure Portal, the new entries look like this:
image

There is one for each Activity.

Expected behavior

It behaves like 1.0.0-beta.12 and they do not get output.

Actual behavior

It gets output.

Reproduction Steps

I linked to the PR.

Environment

Our global.json:

{
  "sdk": {
    "version": "7.0.302",
    "rollForward": "latestMinor",
    "allowPrerelease": false
  }
}

We are using Azure Functions based on this Dockerfile with:

FROM mcr.microsoft.com/azure-functions/dotnet:4.0.1.16816-dotnet6-appservice
@github-actions github-actions bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jul 25, 2023
@cataggar cataggar changed the title [BUG] [BUG] Azure.Monitor.OpenTelemetry.Exporter 1.0.0-beta.13 creates ReadOnlyDictionary messages Jul 25, 2023
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Monitor - Exporter Monitor OpenTelemetry Exporter CXP Attention and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Jul 25, 2023
@github-actions
Copy link

Thank you for your feedback. This has been routed to the support team for assistance.

@navba-MSFT navba-MSFT added Service Attention Workflow: This issue is responsible by Azure service team. and removed CXP Attention labels Jul 26, 2023
@navba-MSFT
Copy link
Contributor

Adding Service team to look into this.

@github-actions
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cijothomas @reyang @rajkumar-rangaraj @TimothyMothra @vishweshbankwar.

@CodeBlanch
Copy link

It looks like Functions has some custom ILogger states which do not implement a template or a formatter which is causing the logs to look strange when captured by OpenTelemetry. I opened a PR to try and get that fixed upstream.

@cataggar
Copy link
Member Author

The upstream PR was merged for Azure/azure-webjobs-sdk. It looks like a couple of different packages need to be updated. As far as I can tell, https://github.com/Azure/azure-functions-host/blob/dev/src/WebJobs.Script/WebJobs.Script.csproj has had Microsoft.Azure.WebJobs updated Azure/azure-functions-host#9541, but still needs Microsoft.Azure.WebJobs.Logging.ApplicationInsights released and updated. Is that correct?

@RohitRanjanMS
Copy link
Member

Hi @cataggar we will plan for a release.

@cataggar
Copy link
Member Author

cataggar commented Oct 3, 2023

@RohitRanjanMS, what is the plan for a release?

@RohitRanjanMS
Copy link
Member

@cataggar , this will be part of the next release.

@cataggar
Copy link
Member Author

cataggar commented Oct 20, 2023

Which release am I waiting for? Is it this one? https://github.com/Azure/azure-webjobs-sdk/releases/tag/appinsights-v3.0.38
Microsoft.Azure.WebJobs.Logging.ApplicationInsights 3.0.38

@cataggar
Copy link
Member Author

This is solved by updating to https://www.nuget.org/packages/Microsoft.Azure.WebJobs/3.0.39 .

@github-actions github-actions bot locked and limited conversation to collaborators Jan 21, 2024
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. customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor - Exporter Monitor OpenTelemetry Exporter needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants