refactor(backends/datadog): avoid useless call to Datadog API #356
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lvaylet
requested changes
Nov 3, 2023
sdenef-adeo
force-pushed
the
refactor/avoid-useless-datadog-api-calls
branch
from
8c03eb3
to
9f49471
Compare
lvaylet
approved these changes
Nov 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
Perf improvement. Avoid calling
/sloendpoint because the response is not used.As discussed, I left the call but I added a condition to run it only in debug mode.
NB: SLO's data are available in the
/slo/historyendpoint call right after this oneRegards,
Sébastien