Replies: 1 comment 3 replies
-
Hi @misterek, yes at the moment the routes configuration applies to both client and server requests. Adding the ability to split them is a good idea, if it's possible please open a feature request. At the moment I can only think of running separate Beyla instances, one that instruments your client app(s) and another one that instruments the server app(s). Each would have separate configuration file, allowing you to customize the routes decorator properties. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Config question -- the beyla docs (https://grafana.com/docs/beyla/latest/configure/options/) mention "You should use the routes property whenever possible to reduce the cardinality of generated metrics."
It seem like the routes property applies to both client and server? Is that correct, and the intended behavior?
Is there any way to have that different for client and server? In one case I'd like to leave the route unset if it's not in the list. In the other case I'd like to use the heuristic.
Beta Was this translation helpful? Give feedback.
All reactions