Skip to content
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

LC monitoring logic #17

Closed
msimonin opened this issue May 20, 2013 · 2 comments
Closed

LC monitoring logic #17

msimonin opened this issue May 20, 2013 · 2 comments

Comments

@msimonin
Copy link
Member

We could need some metrics for the LCs like ( energy, ios...).
Where this logic should go ?
Should each LC reponsible of getting its own metrics and then send them to its GM
or
Should GMs responsible of getting these metrics for all its LCs ?

M

@msimonin
Copy link
Member Author

msimonin commented Jul 2, 2013

If LC is responsible of getting its own metrics (temp, power consumption) a new monitoring service should be added.
We already have

  • heartbeatProducer (one)
  • virtualMachineMonitoringProducer (one per VM)

We should add LocalController[Metric]Producer ( one producer per metric ).

In terms of consumer we have

  • VirtualMachineMonitorConsumer
    maybe we should think changing since it would be responsible of getting vm datas, heartbeat and metrics.

@msimonin
Copy link
Member Author

Duplicate with #24
This feature will be probably added in the next release.

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

No branches or pull requests

1 participant