Configuration to turn the autometrics feature on/off

[pradeepcdlm]

Is there is any single point of configuration to turn the autometrics feature in a code base. What would be the model or pattern we have to use. Why I'm asking this question because in case of a performance bottleneck, and we need to turn this feature off, then what is the best approach we can do.

[IvanMerrill]

Hi Pradeep. Good question! There is no single point of configuration, or a feature flag or similar that could be used to turn autometrics off currently. You would have to do a code deploy after removing the decorators in order to remove the monitoring as it stands.

In terms of performance bottlenecks there have been some performance tests for some of the libraries that I'll try and dig out for you that might alleviate some of your fears. Don't forget that autometrics is built on top of prometheus and OTeL libraries which are already widely used and tested in production!

[pradeepcdlm]

Thanks @IvanMerrill for your quick response. Since the code spread over the entire code base and if we want to disable this due to some reason for example a performance bottleneck , for example. If we have a model like there is a pointcut expression that allows us to define a condition to be checked before execute the autometrics code, just like aspect oriented programming do.

[IvanMerrill]

I completely understand your point! I have added this as an idea on the discussions page. Feel free to add more information to this page if there's anything you would like to add.