Skip to content

Change error logs to debug for trigger type parsing #297

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

Merged
merged 1 commit into from
Nov 8, 2022

Conversation

IvanTopolcic
Copy link
Contributor

@IvanTopolcic IvanTopolcic commented Aug 2, 2022

What does this PR do?

These logs are not technically errors, as they're expected flow in some cases. For example, event bridge triggers do not necessarily need to be ARNs.

Motivation

Testing Guidelines

Additional Notes

Types of Changes

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

Check all that apply

  • 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
  • This PR passes the integration tests (ask a Datadog member to run the tests)

@IvanTopolcic IvanTopolcic requested a review from a team as a code owner August 2, 2022 20:33
@IvanTopolcic IvanTopolcic changed the title Change error logs to debug Change error logs to debug for trigger type parsing Aug 2, 2022
@@ -303,7 +303,7 @@ export function extractTriggerTags(event: any, context: Context) {
try {
eventSourceARN = parseEventSourceARN(eventSource, event, context);
} catch (error) {
logError(`failed to extract ${eventSource} arn from the event`, { error });
logDebug(`failed to extract ${eventSource} arn from the event`, { error });
Copy link
Contributor

Choose a reason for hiding this comment

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

BTW, is there any problem with the way we log { error }? From both user reports, I didn't see any error being logged, which is probably the most valuable part of this log.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah this is actually super confusing because looking at the code all it seems like we're doing is returning a field in an object and somehow an error is being thrown. I've tried to replicate it here.

@codecov-commenter
Copy link

codecov-commenter commented Aug 2, 2022

Codecov Report

Merging #297 (3fefd2e) into main (4ec3816) will not change coverage.
The diff coverage is 33.33%.

@@           Coverage Diff           @@
##             main     #297   +/-   ##
=======================================
  Coverage   80.05%   80.05%           
=======================================
  Files          36       36           
  Lines        1715     1715           
  Branches      387      387           
=======================================
  Hits         1373     1373           
  Misses        290      290           
  Partials       52       52           
Impacted Files Coverage Δ
src/trace/trigger.ts 87.01% <33.33%> (ø)

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

@IvanTopolcic IvanTopolcic merged commit 6a12c46 into main Nov 8, 2022
@IvanTopolcic IvanTopolcic deleted the ivan.topolcic/change-error-logs-to-debug branch November 8, 2022 18:18
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.

3 participants