Monitoring as a Service

Registered by Alexandre Viau on 2014-05-01

Problem to solve: Ceilometer's purpose is to track and *measure/meter* usage information collected from OpenStack components (originally for billing). While Ceilometer is usefull for the cloud operators and infrastructure metering, it is not a *monitoring* solution for the tenants and their services/applications running in the cloud because it does not allow for service/application-level monitoring and it ignores detailed and precise guest system metrics.

Proposed solution: We would like to add Monitoring as a Service to OpenStack Telemetry

Just like Rackspace's Cloud monitoring, the new monitoring service would let users/tenants keep track of their ressources on the cloud and receive instant notifications when they require attention.

This RESTful API would enable users to create multiple monitors with predefined checks, such as PING, CPU usage, HTTPS and SMTP or custom checks performed by a Monitoring Agent on the instance they want to monitor.

Predefined checks such as CPU and disk usage could be polled from Ceilometer. Other predefined checks would be performed by the new monitoring service itself. Checks such as PING could be flagged to be performed from multiple sites.

Custom checks would be performed by an optional Monitoring Agent. Their results would be polled by the monitoring service and stored in a backend (could be Ceilometer).

The project would start with API functions. In the future, it could be integrated into Horizon with statistics and graph functionalities.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Alexandre Viau
Direction:
Needs approval
Assignee:
Alexandre Viau
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
milestone icon next
Completed by
gordon chung on 2015-07-10

Related branches

Sprints

Whiteboard

inactive and scope of blueprint is too large. -- gordc (10.7.15)

(?)

Work Items