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

J hoang/appeals 34906 2 #20405

Merged
merged 1 commit into from
Jan 3, 2024
Merged

Conversation

jonathanh-va
Copy link
Contributor

@jonathanh-va jonathanh-va commented Jan 3, 2024

Resolves 34906

Description

Logging for errors in UAT and fixed error:
undefined local variable or method 'bad_request' for #<CorrespondenceController:0x00007fed5351ccd0>

Acceptance Criteria

  • Code compiles correctly

Best practices

Code Documentation Updates

  • Add or update code comments at the top of the class, module, and/or component.

Tests

Test Coverage

Did you include any test coverage for your code? Check below:

  • RSpec
  • Jest
  • Other

Code Climate

Your code does not add any new code climate offenses? If so why?

  • No new code climate issues added

Monitoring, Logging, Auditing, Error, and Exception Handling Checklist

Monitoring

  • Are performance metrics (e.g., response time, throughput) being tracked?
  • Are key application components monitored (e.g., database, cache, queues)?
  • Is there a system in place for setting up alerts based on performance thresholds?

Logging

  • Are logs being produced at appropriate log levels (debug, info, warn, error, fatal)?
  • Are logs structured (e.g., using log tags) for easier querying and analysis?
  • Are sensitive data (e.g., passwords, tokens) redacted or omitted from logs?
  • Is log retention and rotation configured correctly?
  • Are logs being forwarded to a centralized logging system if needed?

Auditing

  • Are user actions being logged for audit purposes?
  • Are changes to critical data being tracked ?
  • Are logs being securely stored and protected from tampering or exposing protected data?

Error Handling

  • Are errors being caught and handled gracefully?
  • Are appropriate error messages being displayed to users?
  • Are critical errors being reported to an error tracking system (e.g., Sentry, ELK)?
  • Are unhandled exceptions being caught at the application level ?

Exception Handling

  • Are custom exceptions defined and used where appropriate?
  • Is exception handling consistent throughout the codebase?
  • Are exceptions logged with relevant context and stack trace information?
  • Are exceptions being grouped and categorized for easier analysis and resolution?

@jonathanh-va jonathanh-va changed the base branch from master to feature/APPEALS-27311 January 3, 2024 18:49
@jonathanh-va jonathanh-va marked this pull request as ready for review January 3, 2024 18:54
Copy link

codeclimate bot commented Jan 3, 2024

Code Climate has analyzed commit d6921e6 and detected 56 issues on this pull request.

Here's the issue category breakdown:

Category Count
Duplication 9
Complexity 11
Style 34
Bug Risk 1
Performance 1

View more on Code Climate.

@youfoundmanesh youfoundmanesh merged commit 5ac9ff7 into feature/APPEALS-27311 Jan 3, 2024
9 of 15 checks passed
craigrva pushed a commit that referenced this pull request Jan 24, 2024
Co-authored-by: Jonathan Hoang <trinhjoanthan.hoang@va.gov>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants