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
Describe the feature request
Currently there is MeshConfig.accessLogFile which controls logging for the entire mesh. This is fine for small deployments but for larger deployments enabling logging on thousands of sidecars can cause problems for logging infrastructure. It would be ideal to be able to turn on access logging on a per proxy basis either via an annotation, the Sidecar resource and via the command line.
Also for short term debugging it would be great to be able to use istioctl proxy-config log to control access logging
Previously in 1.5.x we were able to configure logging from the istio-ingressgateway via a telemetry rule, handler and instance. Without this functionality we cannot upgrade to telemetry-v2
In our slack thread @howardjohn mentioned telemetry working group had this on their 1.8 roadmap, but let's watch this. This is a much-needed feature and I didn't see any other GH issues that reference it.
I believe #24287 tracks adding telemetry API which includes access log control, and it is a P0 for telemetry working group. If you are ok tracking it there, shall we close this one as duplicated issue?
On Thu, Aug 27, 2020 at 10:13 AM Pengyuan Bian ***@***.***> wrote:
I believe #24287 <#24287> tracks
adding telemetry API which includes access log control, and it is a P0 for
telemetry working group. If you are ok tracking it there, shall we close
this one as duplicated issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#26859 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAM7UM6ZDP2Y2HWWZ3HGSLSC2H2ZANCNFSM4QNDGEYA>
.
Describe the feature request
Currently there is
MeshConfig.accessLogFile
which controls logging for the entire mesh. This is fine for small deployments but for larger deployments enabling logging on thousands of sidecars can cause problems for logging infrastructure. It would be ideal to be able to turn on access logging on a per proxy basis either via an annotation, theSidecar
resource and via the command line.Also for short term debugging it would be great to be able to use
istioctl proxy-config log
to control access loggingPreviously in 1.5.x we were able to configure logging from the istio-ingressgateway via a telemetry
rule
,handler
andinstance
. Without this functionality we cannot upgrade to telemetry-v2Describe alternatives you've considered
istioctl proxy-config log
EnvoyFilter - https://github.com/istio/istio/wiki/EnvoyFilter-Samples#tracing-and-access-logging
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[x] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context
The text was updated successfully, but these errors were encountered: