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.

Sign up for GitHub

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

Jump to bottom

Datadog: LongTaskTimer/Active Interpreted as a Time rather than Occurrence #3511

Closed
darylrobbins opened this issue Nov 3, 2022 · 3 comments · May be fixed by #3880
Closed

Datadog: LongTaskTimer/Active Interpreted as a Time rather than Occurrence #3511

darylrobbins opened this issue Nov 3, 2022 · 3 comments · May be fixed by #3880
Labels
closed-as-inactive registry: datadog A Datadog Registry related issue

Comments

@darylrobbins
Copy link

Describe the bug
The Active statistic for the LongTaskTimer does not override the default units for the metric so it's reported as a time rather than an occurence.

Environment

  • Micrometer version 1.9.5
  • Micrometer registry Datadog
  • OS: Windows
  • Java version: VM information: OpenJDK Runtime Environment 1.8.0_322-b06 Amazon.com Inc. OpenJDK 64-Bit Server VM 25.322-b06

To Reproduce
How to reproduce the bug:
Send a LongTaskTimer metric to Datadog and observe the statistic:active values in Datadog.

Expected behavior
The values should be reported as occurrences.

Additional context
Add any other context about the problem here, e.g. related issues.
@shakuzen shakuzen added the registry: datadog A Datadog Registry related issue label Nov 7, 2022
@darylrobbins darylrobbins mentioned this issue Jun 7, 2023
Open
@marcingrzejszczak
Copy link
Contributor

Thank you for filing this issue! Can you provide a complete, minimal, verifiable sample that reproduces the problem? It should be available as a GitHub (or similar) project or attached to this issue as a zip file. Thank you for your understanding.

@marcingrzejszczak marcingrzejszczak added the waiting for feedback We need additional information before we can continue label Dec 20, 2023
@github-actions GitHub Actions
Copy link

github-actions bot commented Jan 2, 2024

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

@github-actions GitHub Actions
Copy link

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2024
@jonatan-ivanov jonatan-ivanov removed waiting for feedback We need additional information before we can continue waiting-for-triage feedback-reminder labels Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-as-inactive registry: datadog A Datadog Registry related issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Datadog: Align handling of LongTaskTimer with Timer darylrobbins/micrometer
4 participants
@darylrobbins @jonatan-ivanov @marcingrzejszczak @shakuzen