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

feat: Add option for Processor to drop metrics #130

Closed
wants to merge 1 commit into from

Conversation

mycrEEpy
Copy link

@mycrEEpy mycrEEpy commented Mar 9, 2023

What does this PR do?

Add two parameters MetricsChannelCapacity and DropMetricsAtCapacity.

This will allow the AddMetric function to be truly non-blocking even if we risk loosing some metrics.

The default will remain at a channel capacity of 2000 and blocking to wait for capacity.

Motivation

Following the DataDog outage of 2023.03.08 in EU central some of our Lambdas were blocking due to the blocking nature of the AddMetric function in cases where the metricsChan is at capacity.

Testing Guidelines

Added test case TestProcessorBatchesDropMetricsAtCapacity

Additional Notes

Types of changes

  • Bug fix
  • New feature
  • Breaking change
  • Misc (docs, refactoring, dependency upgrade, etc.)

Checklist

  • This PR's description is comprehensive
  • This PR contains breaking changes that are documented in the description
  • This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
  • This PR impacts documentation, and it has been updated (or a ticket has been logged)
  • This PR's changes are covered by the automated tests
  • This PR collects user input/sensitive content into Datadog

@mycrEEpy mycrEEpy requested a review from a team as a code owner March 9, 2023 18:08
This will allow the AddMetric function to be truly non-blocking even if
we risk loosing some metrics.

Signed-off-by: Tobias Germer <tobias.germer@tui.com>
@mycrEEpy mycrEEpy force-pushed the custom-metrics-no-blocking branch from 791ff4d to 522f1e4 Compare March 9, 2023 18:13
@clifordshelton
Copy link

Closing stale PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants