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

Monitoring and logging #3405

Closed
akainic opened this issue Oct 17, 2016 · 14 comments
Closed

Monitoring and logging #3405

akainic opened this issue Oct 17, 2016 · 14 comments
Assignees

Comments

@akainic
Copy link
Contributor

akainic commented Oct 17, 2016

No description provided.

@akainic akainic changed the title Monitoring Monitoring and logging Oct 17, 2016
@akainic
Copy link
Contributor Author

akainic commented Oct 17, 2016

  • Alerting when validation failure occurs (maybe not PagerDuty, look more into CloudWatch)

@akainic
Copy link
Contributor Author

akainic commented Oct 26, 2016

@markolson @lihanli do we have any updates on this?

@lihanli
Copy link
Contributor

lihanli commented Oct 26, 2016

devops added sentry to vets-api, alerts still need to be setup though

@akainic
Copy link
Contributor Author

akainic commented Oct 27, 2016

Things we need to check off here:

  • Create and implement log management plan
  • Define log collection and analysis architecture
  • Test log collection and analysis architecture
  • Define production versus debugging logging standards
  • Document method to enable debugging log level on production system
  • Test enabling different logging levels
  • Verify correct log messages produced at different logging levels

@lihanli
Copy link
Contributor

lihanli commented Oct 27, 2016

devops is adding splunk which will be our log collection and analysis architecture https://github.com/department-of-veterans-affairs/devops/issues/617

the rails logger allows different logging levels. we are outputting all log levels in the production log to have access to all possible information.

logger.debug "Person attributes hash: #{@person.attributes.inspect}"
logger.info "Processing the request..."
logger.fatal "Terminating application, raised unrecoverable error!!!"

Document method to enable debugging log level on production system

Rails.application.configure do
  config.log_level = :debug
end

@akainic
Copy link
Contributor Author

akainic commented Oct 31, 2016

Follow up with devops and make sure we can access the logs and are getting alerts

@akainic
Copy link
Contributor Author

akainic commented Nov 1, 2016

@knkski wanted to loop you into this ticket and make sure that we can access the logs for edu-benefits and that we're getting alerts for issues. Do we need to get access to anything in particular for this?

@lihanli
Copy link
Contributor

lihanli commented Nov 1, 2016

we have access to the logs through cloudwatch. me and mark both have access and tested it out already. i still need to set up sentry access and test out alerts though

@lihanli
Copy link
Contributor

lihanli commented Nov 1, 2016

i'm registered on sentry and subscribed to alerts now

@knkski
Copy link
Contributor

knkski commented Nov 1, 2016

If anybody else needs CloudWatch access, just file a ticket over in the devops repo. As far as alerting, we are sending alerts currently whenever the server gives a 500 error. Will the validation failure alerts that you'd like above be included in that?

@akainic
Copy link
Contributor Author

akainic commented Nov 1, 2016

Got it, thanks @lihanli and @knkski for that information! I think we need some kind of alerting when a validation failure occurs, but I'm not sure what the right tool is for this. @lihanli do you have thoughts on this?

@lihanli
Copy link
Contributor

lihanli commented Nov 1, 2016

i made a pr to add the validation errors to sentry which can send out alerts when they happen department-of-veterans-affairs/vets-api#404

@akainic
Copy link
Contributor Author

akainic commented Nov 1, 2016

Awesome, thanks @lihanli!

@akainic
Copy link
Contributor Author

akainic commented Nov 1, 2016

As all of these items are checked off now, going to close this ticket.

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

No branches or pull requests

4 participants