support events
Events are valuable for understanding system state, so we need to continue to support them. Change-Id: I15f2675a3538c38c834284e1c73decebff5521ed
This commit is contained in:
parent
843e17ccaf
commit
6b0318e9c7
@ -27,17 +27,14 @@ from ceilometer.i18n import _
|
||||
OPTS = [
|
||||
cfg.StrOpt('definitions_cfg_file',
|
||||
default="event_definitions.yaml",
|
||||
deprecated_for_removal=True,
|
||||
help="Configuration file for event definitions."
|
||||
),
|
||||
cfg.BoolOpt('drop_unmatched_notifications',
|
||||
default=False,
|
||||
deprecated_for_removal=True,
|
||||
help='Drop notifications if no event definition matches. '
|
||||
'(Otherwise, we convert them with just the default traits)'),
|
||||
cfg.MultiStrOpt('store_raw',
|
||||
default=[],
|
||||
deprecated_for_removal=True,
|
||||
help='Store the raw notification for select priority '
|
||||
'levels (info and/or error). By default, raw details are '
|
||||
'not captured.')
|
||||
|
@ -31,7 +31,6 @@ OPTS = [
|
||||
),
|
||||
cfg.StrOpt('event_pipeline_cfg_file',
|
||||
default="event_pipeline.yaml",
|
||||
deprecated_for_removal=True,
|
||||
help="Configuration file for event pipeline definition."
|
||||
),
|
||||
]
|
||||
|
@ -8,4 +8,4 @@ sources:
|
||||
sinks:
|
||||
- name: event_sink
|
||||
publishers:
|
||||
- gnocchi://
|
||||
- panko://
|
||||
|
@ -6,9 +6,6 @@ In addition to meters, the Telemetry service collects events triggered
|
||||
within an OpenStack environment. This section provides a brief summary
|
||||
of the events format in the Telemetry service.
|
||||
|
||||
.. warning::
|
||||
Events support is deprecated.
|
||||
|
||||
While a sample represents a single, numeric datapoint within a
|
||||
time-series, an event is a broader concept that represents the state of
|
||||
a resource at a point in time. The state may be described using various
|
||||
|
@ -25,11 +25,6 @@ Events vs. Samples
|
||||
In addition to Meters, and related Sample data, Ceilometer can also process
|
||||
Events.
|
||||
|
||||
|
||||
.. warning::
|
||||
Events support is deprecated.
|
||||
|
||||
|
||||
While a Sample represents a single numeric datapoint, driving a Meter that
|
||||
represents the changes in that value over time, an Event represents the state
|
||||
of an object in an OpenStack service (such as an Instance in Nova, or an Image
|
||||
|
Loading…
x
Reference in New Issue
Block a user