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
Context: we run gotenburg in a kubernetes cluster as part of an overall deployment which includes other microservices that sit "in front" of gotenburg. Currently gotenburg is running fine, but when we go to pull logs they are almost completely unusable because every time we've healthcheck-ed it via a /ping that adds a log line to the output.
Obviously we can pull the logs and grep, but it is a bit annoying given that we have no need to understand that a ping happened cause we can pull that information from kubernetes events.
The text was updated successfully, but these errors were encountered:
* skip logging when healthcheck url is called; closes#74
Signed-off-by: Casey Kuhlman <casey@monax.io>
* skip logging when healthcheck url is called; closes#74
Signed-off-by: Casey Kuhlman <casey@monax.io>
* adds the ability to establish the listen port via env var
Signed-off-by: Casey Kuhlman <casey@monax.io>
…ISTEN_PORT (#78)
* skip logging when healthcheck url is called; closes#74 (#75)
Signed-off-by: Casey Kuhlman <casey@monax.io>
* Configure listen port via environment variable (#77)
* skip logging when healthcheck url is called; closes#74
Signed-off-by: Casey Kuhlman <casey@monax.io>
* skip logging when healthcheck url is called; closes#74
Signed-off-by: Casey Kuhlman <casey@monax.io>
* adds the ability to establish the listen port via env var
Signed-off-by: Casey Kuhlman <casey@monax.io>
* minor refactoring of @compleatang work
* fixing typo
Context: we run gotenburg in a kubernetes cluster as part of an overall deployment which includes other microservices that sit "in front" of gotenburg. Currently gotenburg is running fine, but when we go to pull logs they are almost completely unusable because every time we've healthcheck-ed it via a
/ping
that adds a log line to the output.Obviously we can pull the logs and grep, but it is a bit annoying given that we have no need to understand that a ping happened cause we can pull that information from kubernetes events.
The text was updated successfully, but these errors were encountered: