Skip to content
This repository has been archived by the owner on Nov 8, 2022. It is now read-only.

The task should immediately start collecting the new metrics after a plugin is loaded that shares the same namespace #832

Closed
IzabellaRaulin opened this issue Apr 5, 2016 · 1 comment

Comments

@IzabellaRaulin
Copy link
Contributor

The scenario which presents that:
Step1: Load PluginA
Step2: Create/start Task1 with "intel/*"
=> Task1 is collecting all metrics from PluginA

Step3a: Load PluginB1
=> Task1 should immediately start collecting the new metrics from PluginB1
In current implementation (PR #803) the metrics are being collected only from pluginA

Step3b: Load PluginB2 which requires config
=> Task1 should immediately start collecting the new metrics from PluginB2, but Task1 does not contain any config for the pluginB2, so after 10 times not receiving the metrics from this plugin, the Task1 will fail (@jcooklin approved that the initial task which was valid isn’t now so it seems reasonable that it would fail)

@IzabellaRaulin
Copy link
Contributor Author

Resolved among others by #1146

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants