[BUG] "PartitionId" is mispelled as "PartionId" in EventHubTriggerInput logs

[the-m4a]

Library name and version

Azure.Messaging.EventHub 6.3.5

Describe the bug

Minor issue only observed in logs:

In the GetTriggerDetails function, the label for the PartitionId is mispelled as "PartionId":

{ "PartionId", context.PartitionId },

The label appears in various messages in App Insights related to the Event Hub Triggers, as well as the customDimensions field.

I am opening this bug entirely because I was trying to put together a query using Partition ID as one of the columns and spent a few minutes wondering why "customDimensions.prop__PartitionId" was showing as empty.

Link to the line:

azure-sdk-for-net/sdk/eventhub/Microsoft.Azure.WebJobs.Extensions.EventHubs/src/Triggers/EventHubTriggerInput.cs

Line 86 in 6fcabfc

{ "PartionId", context.PartitionId },

Expected behavior

The label should be "PartitionId". It appears it has been mispelled for as long as this file has existed in this repo.

Actual behavior

Example output from App Insights, message field:

CustomDimensions field:

Reproduction Steps

Enable App Insights Logging for any Azure function that uses an Event Hub trigger and the Azure.Messaging.EventHub package.

Environment

All environments

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[jsquire]

Hi @the-m4a. Thanks for reaching out and letting us know. You're correct in that the misspelling has been present since the original move to this repository in 2020. That makes it a bit tricky, as a straight fix has a high risk of breaking existing applications that rely on the misspelling. I've opened #48517 which works around that by adding a new member with the correct spelling. I do want to get thoughts from the folks who own the Azure Functions host+platform before moving forward, though, as the extension has no insight nor influence over what Functions does with that data.

[jsquire]

fixed by #48517 and will be included in our next release. Release timing is unknown at present.

[github-actions]

Hi @the-m4a. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.