-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for different collect intervals #56
Comments
@cyrille-leclerc I am probably going to work on this shortly. What are your thoughts? I'm leaning towards supporting a |
Thanks! FYI I am working on introducing the Resource API (HTTP, Classpath & File Cyrille On Thu, Feb 4, 2016 at 4:22 PM, Kristoffer Erlandsson <
Cyrille Le Clerc |
Implemented in 1.2.3. |
We would like to collect some of our metrics more frequently than others. Hence we would like support for specifying different collect intervals.
If we can agree on how it should work we are prepared to implement it. The most simple solution I see is to allow for an override on
query
andinvocation
elements:This override would be used when specified. The default would be used for queries which do not have an override.
Another option would to add support for groups of queries/invocations where some configuration parameters could be overridden on group level. Something like:
While I can see the benefits of groups in overriding other parameters (e.g. distinct output writers per group), it is a larger change which adds a bit of complexity.
Any thoughts on this?
The text was updated successfully, but these errors were encountered: