envoyproxy
Did flag `uf_urx` change to `urx_uf`?
If you are reporting any crash or any potential security issue, do not open an issue in this repo. Please report the issue via emailing [email protected] where the issue will be triaged appropriately.
Title: *Did flag uf_urx change to urx_uf? *
Description:
Our dashboard are no longer working and we realized because the flag is now urx_uf. We are using istio 1.24 and envoy v1.32.
uf first makes sense as it is the general error with the urx being more details.
I think this is a combination of UF and URX, and it is possible that the order is changed during the combination in data plane.
cc @wbpcode
Great thank you! I also opened a ticket with DD to see if something changed. But I believe they pull it right from the prom endpoint.
No, I was waiting for the team to chime in if it changed. We are only seeing the new way now.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Yeah, this is an unexpected change of the output. In the original implmentation, we convert this to string based on the order of the flag index. In the new implementation, we convert this to string based on the order of setting flag.
I think this could be treat as a bug and fixed it with a minor PR.
Ok, we updated our dashboard to include both ways. We just weren't sure which is correct and want to monitor the correct metric. Thanks for your help. We will follow along.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
@wbpcode Does it needed to be tracked as a bug and needs to be fixed or do we think that the new behavior is acceptable as its just an ordering change?
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.