Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Unfortunately, I forgot about storeByForeignSource which has a completely different format for resource ID.
I've tested all the changes with a running environment to be sure that the ID works no matter if we have storeByForeignSource enabled or not.
Alejandro Galue October 17, 2013 at 4:33 PM
The attached screenshot shows the new parameters added to the thresholds.
Alejandro Galue October 17, 2013 at 4:32 PM
Fixed on revision 2d1ab5441b100078106545ef852732abdd44e4a4 for 1.12.
Bonus Feature:
After reloading the thresholds configuration, if a threshold is triggered, an immediate rearm with value=NaN will be sent to clear the threshold with the old settings.
Now, instead of value=NaN, you are going to see: value=NaN (the threshold definition has been changed)
The following revisions are also related with this feature:
cce55e8d373f26d4359d0209ff46e1664fe6d0d5
f132a0c34365dd667c82f40ce67bc163cec761e2
d46ccf5f65e7f6ab6fb1638a51086613ea92cf6e
5db14545b40ae4ed6c9d02d94c22022b600e1b90
Unfortunately, I forgot about storeByForeignSource which has a completely different format for resource ID.
I've tested all the changes with a running environment to be sure that the ID works no matter if we have storeByForeignSource enabled or not.