Skip to content

HTTP 502 errors from NodeNorm RENCI #337

@gaurav

Description

@gaurav

We're seeing 502 errors on NodeNorm RENCI.

Next step:

  • Confirm whether this is a Sterling ingress issue or a NodeNorm issue (by seeing if the 502s are in our logs as well).
  • Confirm whether this is related to either Sterling incoming traffic levels (if it is a Sterling ingress issue) or NodeNorm traffic or something else.
  • It might be useful to provide a NodeNorm dashboard that taps into NodeNorm logs to answer questions about 502 error rates, CPU/memory issues and others.
  • If it is a traffic issue, consider using API keys to monitor NodeNorm traffic.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions