You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
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
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:
The text was updated successfully, but these errors were encountered: