Skip to content

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

Closed
@cataggar

Description

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

Metadata

Assignees

No one assigned

    Labels

    ClientThis issue points to a problem in the data-plane of the library.Monitor - ExporterMonitor OpenTelemetry ExporterService AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions