Lahiru Udayanga

Results 16 issues of Lahiru Udayanga

I used this repo to build a live social wall for an event in my university. But today after 3 months, I tried it again for the same hashtag and...

I have written a WASM filter and use `envoyproxy/envoy-build-ubuntu` docker image to build the WASM module as a `proxy_wasm_cc_binary`(mount the source files into the container, build inside and mount back...

Any example for how to use gRPC bidi streams from a wasm filter ? As I understand we can make gRPC calls from either Context or RootContext.

Hello, I am trying to build the http filter with envoy v1.16.0 . I tried using both **gcc** and **clang** but still no luck. ### GCC My specs are as...

### Problem OpenTelemetry tracer not available in envoy proxy version `v1.20.2`. ### Solution Upgrade envoy proxy version from `v1.20.2` to `v1.23.0` to add OpenTelemetry tracing support. ### Implementation _No response_...

Type/Improvement
Priority/Normal

### Purpose Currently WSO2 Choreo Connect supports distributed tracing with Jaeger, Zipkin and Azure Application Insights using the OpenTelemetry SDK and relevant exporters. With this PR, support for publishing traces...

Type/New Feature

### Purpose Eliminate duplicate cluster creation when production and sandbox endpoints are the same ### Issues Fixes https://github.com/wso2/product-microgateway/issues/3002 ### Automation tests - Unit tests added: Yes - Integration tests added:...

Type/Improvement

### Purpose Prevent x-envoy headers `x-envoy-original-path` and `x-envoy-expected-rq-timeout-ms` being sent to the backend ### Issues Fixes https://github.com/wso2/product-microgateway/issues/2986 ### Automation tests - Unit tests added: No - Integration tests added: Yes...

Choreo

### Describe your problem(s) Add support for OpenTelemetry OTLP trace exporter ### Describe your solution Implement a new trace exporter based on OpenTelemetry SDK ### How will you implement it...

Type/New Feature
Priority/Normal

### Description: Endpoints without a basepath not working as expected ### Steps to reproduce: 1. Start a echo service as a test backend `docker run -p 8000:8000 -e PORT=8000 --rm...

Type/Bug
Priority/Normal