How to handle logging #26
Unanswered
WillieCubed
asked this question in
Ideas
Replies: 2 comments
-
This seems like a really good solution. Ignoring the cost of the service, I would be completely for it. The cost seems quite high given the limitations we are trying to place on our projected monthly cost. If this is within our budget lets go for it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Evidently, more research into how Cloud Run works suggests that we can just use a simple STDOUT logger like morgan since GCP with automatically route all STDOUT and STDERR logging to Cloud Logging. Given our current position, this seems like a much more economically viable option. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For a full 1.0 release of the Nebula API, we're going to need some ability to monitor the uptime of the API along with any errors that rise from its operation. As we're intending to use stateless containers to handle API responses, we'll be unable to use log files.
I recommend a third-party service like Sentry to avoid having to easily monitor errors when they arise, triage them and link them to GitHub issues, and use a well-documented API to implement this at all levels of our stack. Additionally, something like this would allow us to centralize logging for all Project Nebula services to make maintenance simpler in the long run.
@CharlieMahana, what do you think?
Beta Was this translation helpful? Give feedback.
All reactions