Customer feature request:
It would be wonderful to have a configuration key ignore: which accepts an array of endpoints to be excluded from instrumentation by the Scout Agent.
I understand implicitly including all controllers by default by adding the use ScoutApm.Instrumentation macro to the myapp_web/myapp_web.ex module as a catch-all for controller actions, but I have a liveness/readiness ping uptime monitoring endpoint that is pinged very frequently by my Kubernetes cluster, and I don't care about that endpoint's metrics (nor do I want those pings to eat up thousands of my paid plan's transactions per day!)
Customer feature request: It would be wonderful to have a configuration key
ignore:which accepts an array of endpoints to be excluded from instrumentation by the Scout Agent.I understand implicitly including all controllers by default by adding the
use ScoutApm.Instrumentationmacro to themyapp_web/myapp_web.exmodule as a catch-all for controller actions, but I have a liveness/readiness ping uptime monitoring endpoint that is pinged very frequently by my Kubernetes cluster, and I don't care about that endpoint's metrics (nor do I want those pings to eat up thousands of my paid plan's transactions per day!)Similar or near-identical implementation to the Ruby Gem for Scout's
config/scout_apm.ymlbut rather in a Phoenix app'sconfig/scout_apm.exswould be wonderful!Love the service so far! Keep up the great work.