Ashutosh Narkar

If you see any missing ones feel free to update. We keep on adding more metrics and probably the doc hasn't been updated.

> Also does OPA emit a metric for number of http.send() calls in each policy execution. I don't think so. There is a metric around inter-query cache hits. It would...

Thanks for the detailed issue @itayhac. I tried to reproduce this by running OPA on docker and setting a 4GB memory limit. I increased the number of go routines from...

One thing I noticed in the policy is you're using the `object.get` builtin on the data set instead of just accessing under `data.rules` for example. You can probably avoid using...

@itayhac can you please confirm if you're able to repro this issue with the upstream OPA images including any differences with the `static` variant. You mentioned (in a separate thread)...

This could be related to https://github.com/open-policy-agent/opa/issues/5946. In your policy you're referring to a large object and this can be replicated if you modify the policy to refer to the object...

The data has some objects and arrays and I wonder if when referenced inside of the policy the interface-AST conversions are impacting performance in terms of CPU and memory.

We're looking to implement something like discussed in https://github.com/open-policy-agent/opa/issues/4147. This should probably help with performance as we'll avoid the interface to AST conversion during eval.

@itayhac are you able to repro this with OPA v0.67.0? I was unable to repro this so would be good to verify incase I missed something.

This is an error coming from the rego package and it's handled differently. [This](https://github.com/open-policy-agent/opa/blob/main/cmd/eval.go#L281) is why it goes to stdout. This is printed by the presentation package. We can probably...