Git Product home page Git Product logo

Comments (6)

xcbeyond avatar xcbeyond commented on August 24, 2024

I encountered the same problem

from proxy-wasm-go-sdk.

Ien001 avatar Ien001 commented on August 24, 2024

same problem.

for me, seems like the beheavior is not linear, some lines of logging are executed, while the others are not.

from proxy-wasm-go-sdk.

pvmraghunandan avatar pvmraghunandan commented on August 24, 2024

Any update on this? Facing the same problem that only Warning logs are visible

from proxy-wasm-go-sdk.

M4tteoP avatar M4tteoP commented on August 24, 2024

I did it a go by adding a test that prints logs: main...M4tteoP:proxy-wasm-go-sdk:logs_levels.
With a standalone envoy, everything seems to be working as expected:

▶ envoy --version
envoy  version: 816188b86a0a52095b116b107f576324082c7c02/1.30.1/Distribution/RELEASE/BoringSSL
▶ make run name=logs_levels
[...]
wasm log: It's 1718378068872354000: random value: 10160872717141755441
wasm log: OnTick called with LogInfof
wasm log: OnTick called with LogDebug
wasm log: OnTick called with LogInfo
wasm log: OnTick called with LogWarn
wasm log: OnTick called with LogError
wasm log: OnTick called with LogCritical

Based on istio doc, Envoy 1.28 is the one used in Istio 1.20:

▶ envoy --version
envoy  version: b5ca88acee3453c9459474b8f22215796eff4dde/1.28.0/Distribution/RELEASE/BoringSSL
▶ make run name=logs_levels
[...]
wasm log: It's 1718378193020451000: random value: 4166824581932656402
wasm log: OnTick called with LogInfof
wasm log: OnTick called with LogDebug
wasm log: OnTick called with LogInfo
wasm log: OnTick called with LogWarn
wasm log: OnTick called with LogError
wasm log: OnTick called with LogCritical

Are you all facing the issue in Istio 1.20 or can you reproduce it on a standalone envoy?

from proxy-wasm-go-sdk.

pvmraghunandan avatar pvmraghunandan commented on August 24, 2024

I am having logs issue (only warning logs are displayed) only after applying the WASM filter to the istio ingress gateway. Standalone envoy when ran as docker container worked fine with emitting info logs and debug when -l is set. Is there any specific configuration to be set to vm or filter config when applied to ingress gateway?

from proxy-wasm-go-sdk.

mathetake avatar mathetake commented on August 24, 2024

I don't think this is a SDK specific issue, please ask in either Istio or Envoy slack instead.

from proxy-wasm-go-sdk.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.