Skip to content
This repository was archived by the owner on Mar 26, 2025. It is now read-only.
This repository was archived by the owner on Mar 26, 2025. It is now read-only.

Better error logging for hub operations #323

Open
@wileyj

Description

@wileyj

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"
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementIterations on existing features or infrastructure.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions