service-mesh

overview

Today, the RequestRecorder records service RPC calls. If those take less than < 0ms, the recorder marks them as 0ms.

proposal

Make the RequestRecorder report the elapsed time for service calls that take less than < 0ms as decimal values, instead of 0.

notes

testing

If you take this on, I'd kindly advise to start in a TDD fashion. Write a test

这样很方便查看

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

The plugin HttpPlugin of nodejs agent not intercept the method http.get

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

What problem are you trying to solve?

Under some configs, Grafana charts making use of the [i]rate function aren't displaying any data.

How should the problem be solved?

This happens when time duration parameters in promql queries are smaller than the scrape interval Prometheus is configured with. The solution is detailed in [this blog post](https://grafana.com/blog/2020/09/28/new-in-

Is your feature request related to a problem? Please describe.

This is the logic currently implemented in the main branch:

If headers criteria are configured, a request is filtered in if it matches both headers and urls. If headers criteria are NOT configured, the probability options are used.

Describe the solution you'd like

I want to take the URL check when no header is

The New Feature

2021-10-22 14:34:05,140 [DEBUG] [21,ac1bd917163488444513910172628] [proxy] [upstream] append headers: GET / HTTP/1.1

1. support upstream connection id.
2. xx

Your scenes

Describe your use scenes (why need this feature).

Your advice

Describe the advice or solution of this new feature.

Environment

• MOSN Version

Some pages give React warnings when you visit them and inspect the dev console. This is probably minor but would be good to resolve.

Services page:

Istio Config details page:
![Screenshot from 2022-03-04 12-15-03](https://user-images.githubusercontent

What happened?

As parsing time.Duration works only with time periods (i.e 1m, 24h, 23h59m etc.) you cannot specify period in days/months/years as we suggests in help/docs of our commands:
https://github.com/kumahq/kuma/blob/8708885a8ef244f0806aa7d5dae08c7dde64a7bb/app/kumactl/cmd/generate/generate_zoneingress_token.go#L29
we can fix it by changing flag description/help, but I think we

Bug description:

If the ca cert or private key contained in the CA bundle secret is configured incorrectly and Tresor is the cert provider, a segmentation fault will occur when

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Add a sample of MMS using a custom model server similar to sklearn and triton that will reside [in

Current Behavior

Desired Behavior

Appbar should not overlap with breadcrumbs navigation, it should remain under it, attached with the form.

Screenshots/Logs

Environment

• Browser:

Version

1.2.x (latest stable)

Describe the requested changes

The following link is broken in meshctl check output:

🟡 Gloo Mesh Agents Connectivity
    Hints:
    * No registered clusters detected. To register a remote cluster that has a deployed Gloo Mesh agent, add a KubernetesCluster CR.
      For more info, see: https://docs.solo.io/gloo-mesh-enterprise/latest/setup/clus

Create an example walkthrough that focuses on TCP based routing with TLS support.