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

Better error logging for hub operations #323

Open
wileyj opened this issue Feb 11, 2021 · 0 comments
Open

Better error logging for hub operations #323

wileyj opened this issue Feb 11, 2021 · 0 comments
Labels
enhancement Iterations on existing features or infrastructure.

Comments

@wileyj
Copy link
Contributor

wileyj commented Feb 11, 2021

Describe the bug
Using an nginx proxy, it's nearly impossible to correlate an nginx 500 error to an error on a hub outside of using a timestamp.

Adding a path item or something else identifiable would be helpful in linking a proxy error to an event in the hub log.

ex:

{
  "message": "Expected isPoint, got Buffer",
  "__type": "isPoint",
  "__value": {
    "type": "Buffer",
    "data": [
        00
    ]
  },
  "__valueTypeName": "Buffer",
  "level": "error",
  "timestamp": "2021-02-11 16:26:41",
  "path": "/hub/xxxxxxx/something.json"
}
@criadoperez criadoperez added feature Brand new functionality. New pages, workflows, endpoints, etc. enhancement Iterations on existing features or infrastructure. and removed feature Brand new functionality. New pages, workflows, endpoints, etc. labels Apr 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Iterations on existing features or infrastructure.
Projects
None yet
Development

No branches or pull requests

2 participants