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
Some logs like fe.internal.logfe.gc.log.20240605-094644 are not print to stdout even when LOG_CONSOLE=1 is set.
One way to get it to datadog is to tail it from a sidecar container and leverage datadog agent to upload it to DD backend
Describe the solution you'd like
Have an option in the helm values.yaml file to allow mounting log volume to sidecar
Additional context
Add any other context or screenshots about the enhancement here.
The text was updated successfully, but these errors were encountered:
The sidecar is fully open, allowing users to attach any volume to the sidecar themselves.
In helm values.yaml, you can check how log volume name is named.
Describe the problem
Some logs like
fe.internal.log
fe.gc.log.20240605-094644
are not print to stdout even whenLOG_CONSOLE=1
is set.One way to get it to datadog is to tail it from a sidecar container and leverage datadog agent to upload it to DD backend
Describe the solution you'd like
Have an option in the helm values.yaml file to allow mounting log volume to sidecar
Additional context
Add any other context or screenshots about the enhancement here.
The text was updated successfully, but these errors were encountered: