When checking for the limit of attributes, the count is including all internal attributes that the integration adds to the metricSet and this causes confusion to the customers.
Expected Behavior
Internal attributes should not count to the limit, only attributes of the "beans" that are fetched
Steps to Reproduce
Run the integration with a metric_limit of 1
Configure a collection file with with a single domain and a query
Add a single attribute to be fetched
The integration will say that it won't report the domain because it's over the limit (the limit will be shown as a lot higher that 1, the attribute/metric we want collected
Description
When checking for the limit of attributes, the count is including all internal attributes that the integration adds to the metricSet and this causes confusion to the customers.
Expected Behavior
Internal attributes should not count to the limit, only attributes of the "beans" that are fetched
Steps to Reproduce
Run the integration with a metric_limit of 1 Configure a collection file with with a single domain and a query Add a single attribute to be fetched
The integration will say that it won't report the domain because it's over the limit (the limit will be shown as a lot higher that 1, the attribute/metric we want collected