Replies: 0 comments 1 reply
-
Hi @shayyxi thanks for the suggestion! We definitely could add an option for this, though I'd be curious about the exact use case for it. Right now, we're only tracking 2 metrics per function by default. The most expensive is the histogram for tracking latency, but I'd probably want to hear a specific use case for skipping that before adding more options to the library. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I came to know about this cool instrumentation framework while visiting your Kubecon booth. While visiting some other booths, there were some tools focused on controlling the metrics quantity reaching the datastore for data cost-saving purposes. Which basically gave me this idea I am going to share here. I was thinking about the ability in this framework to suppress some specific metrics for a function. In this way, if a developer is not interested in some specific metrics for some specific function, they can suppress those specific metrics for that function.
What do you guys think about this?
Beta Was this translation helpful? Give feedback.
All reactions