Skip to content

Conversation

gansb
Copy link
Contributor

@gansb gansb commented Oct 23, 2024

Description

When publishing as prometheus metrics the kafka gauge metrics are exported as

# TYPE messaging_kafka_consumer_queue_message_count_Number of ops (callbacks, events, etc) waiting in queue for application to serve with rd_kafka_poll() gauge
# UNIT messaging_kafka_consumer_queue_message_count_Number of ops (callbacks, events, etc) waiting in queue for application to serve with rd_kafka_poll() Number of ops (callbacks, events, etc) waiting in queue for application to serve with rd_kafka_poll()
messaging_kafka_consumer_queue_message_count_Number of ops (callbacks, events, etc) waiting in queue for application to serve with rd_kafka_poll()

This may be because the description is passed as a unit.

Fixes #6447

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
    • No. Follow-up changes expected.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • Yes
    • No
  • Did you add public API?
    • Yes
      • If yes, did you have an API Review for it?
        • Yes
        • No
      • Did you add <remarks /> and <code /> elements on your triple slash comments?
        • Yes
        • No
    • No
  • Does the change make any security assumptions or guarantees?
    • Yes
      • If yes, have you done a threat model and had a security review?
        • Yes
        • No
    • No
  • Does the change require an update in our Aspire docs?
    • Yes
      • Link to aspire-docs issue:
    • No
Microsoft Reviewers: Open in CodeFlow

@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates that the PR has been added by a community member label Oct 23, 2024
@gansb gansb changed the title Don't pass the gauge description as a unit Don't pass meter descriptions as units Oct 23, 2024
@gansb
Copy link
Contributor Author

gansb commented Oct 23, 2024

@dotnet-policy-service agree

@mitchdenny
Copy link
Member

@samsp-msft @JamesNK

@JamesNK
Copy link
Member

JamesNK commented Oct 23, 2024

Copy link
Member

@eerhardt eerhardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to have a test. Can be done as a follow up.

@davidfowl
Copy link
Member

Does this need to be backported?

@JamesNK JamesNK merged commit c3cdb10 into dotnet:main Oct 24, 2024
9 checks passed
@JamesNK
Copy link
Member

JamesNK commented Oct 24, 2024

@gansb Thanks for the fix!

@eerhardt Can you manage getting this backported to 9.0?

@davidfowl
Copy link
Member

/backport to release/9.0

Copy link
Contributor

Started backporting to release/9.0: https://github.com/dotnet/aspire/actions/runs/11492020195

@github-actions github-actions bot locked and limited conversation to collaborators Nov 23, 2024
@github-actions github-actions bot added the area-integrations Issues pertaining to Aspire Integrations packages label Mar 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-integrations Issues pertaining to Aspire Integrations packages community-contribution Indicates that the PR has been added by a community member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Aspire.Confluent.Kafka publishes broken metrics
5 participants