| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
... because the attribute was deprecated a long ago and no longer
available since oslo.context 4.0.0[1].
[1] f4cbe4c296f4dd23c451a5804a70f639cd8976d6
Change-Id: Ica26126946633f54ecb04c8c0414633332785fab
|
|
|
|
|
|
|
|
|
|
|
| |
The oslo_utils.fnmatch module was added to solve an issue in py2.7 but
it is no longer required because py2.7 is no longer supported.
The module was deprecated since oslo.utils 4.9.1[1] and the stdlib's
fnmatch module should be used instead.
[1] 4c893c92f551c9dd2a7cfbe7ae8171ad8139df0b
Change-Id: Ibae52796df829f151c3088026a326deaf859bd44
|
|
|
|
|
|
| |
Co-authored by: Matthias Runge <mrunge@redhat.com>
Change-Id: I85a4d79396874670f1b36cb91cfba5da812c2839
|
|
|
|
|
|
|
| |
Events are valuable for understanding system state, so we need to
continue to support them.
Change-Id: I15f2675a3538c38c834284e1c73decebff5521ed
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Iadda5e51d61c44c4dd11d7fc82bc7938f74baa5c
|
|/
|
|
|
|
|
| |
This subsystem has never been finished and is not maintained.
Deprecate it for future removal.
Change-Id: I934696b8fc066adc2d9085c64dffb3759fa4489c
|
|
|
|
|
|
| |
make samples and events use a common endpoint class
Change-Id: I1d15783721f91ee90adfbac88cef2a44e0b23868
|
|
|
|
| |
Change-Id: I6b262dd440a72f25662b64d938ab9e5328709a97
|
|
|
|
|
|
|
| |
There is no more storage in event, and the models are used just to manipulate
Event objects, so let's move it out of this folder.
Change-Id: I43c34857518e5e71728c63f20e10508e5d1dd8d7
|
|
|
|
|
|
|
|
|
|
|
|
| |
process notifications as is. this should not impact upgrades as
this does not change what is outputed by notification agent in
any way, just how it does initial processing.
note, this *will* change what is stored in Events if raw field is
enabled. that said, the raw field is unqueryable from Panko pov and
it actually is storing the raw message now.
Change-Id: If79f91687c6c1bc27d906045573674b002534ab1
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
all our code assumes we're using oslo.messaging message wrapper
which has a timestamp, event_type, priority, payload. there exists
code in event generation that allows for timestamp to be missing but
this is impossible unless someone recreated the oslo.messaging format
and for some reason just wanted to see the world burn and left out
the timestamp.
let's just only handle 100% oslo.messaging.
Change-Id: I530e7947e9d71370c14f1484724630b2a8edc059
|
|
|
|
|
|
|
|
|
|
|
|
| |
Log messages are no longer being translated. This removes all use of
the _LE, _LI, and _LW translation markers to simplify logging and to
avoid confusion with new contributions.
See:
http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002574.html
http://lists.openstack.org/pipermail/openstack-dev/2017-March/113365.html
Change-Id: I836a018f971fb71bfa35e76f00433a263440de18
|
|
|
|
|
|
|
|
|
|
| |
We have moved the pipeline config files from etc/ceilometer/ to
ceilometer/pipeline/data/, but ceilometer don't support to load pipeline
config file from /etc/ceilometer/ and only support to load these config
files from the source code path. This is not user-friendly.
Change-Id: Iedebf6b05e123c94eb7bd200f64beb09382c3969
Closes-Bug: #1670238
|
|
|
|
|
|
|
| |
Ship YAML files except for polling.yaml to /usr/share
so that users can update on upgrade.
Change-Id: I642a5f70d940e3e463d58d4a67fb02a5ff415404
|
|
|
|
|
|
| |
This now has been moved to Panko.
Change-Id: I179eb0d436752e3bb8abaed714664cf74f5615e6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This remove pollsters option from configfile sample
due to a duplicate option registration. This will
be fixed later.
The exchange_control group in the config sample doesn't exit
in reality exchange are in DEFAULT group.
This removes usage of cfg.CONF everywhere left.
This adds all missing OPTS in sample file.
Change-Id: I48c11ee7e1aae65847958b98532b3bdb48a3ceb5
|
|
|
|
| |
Change-Id: Iadfc21edd63b9e8c529691c1ccb150b23d3ee8d4
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
String interpolation should be delayed to be handled by the logging code,
rather than being done at the point of the logging call.
Ref:http://docs.openstack.org/developer/oslo.i18n/guidelines.html#log-translation
For example:
# WRONG
LOG.info(_LI('some message: variable=%s') % variable)
# RIGHT
LOG.info(_LI('some message: variable=%s'), variable)
Change-Id: I388cc9262a64a8cda48c8bb342004c62a85dd771
|
| |
| |
| |
| | |
Change-Id: I3f2213932db465ec8e0c7d4f6bdd07f3c4988be8
|
|/
|
|
| |
Change-Id: Ie2d4b7173e8a26f095c0eba44b3d5368d20968bd
|
|
|
|
| |
Change-Id: Ic000ae224cecd0fbf1db4b7068db5bfc468b3507
|
|
|
|
|
|
|
| |
This avoids creating the full table of the old Ceilometer alarms stuff on fresh
install, while upgrade will just ignore them.
Change-Id: I06f825d9a65da46fb7c30fd07c706ee018098b83
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We use debtcollector to mark some DefinitionException classes, such as
EventDefinitionException, deprecated to declarative.DefinitionException,
while we never use them. In fact, declarative.DefinitionException is
the deprecated one, we should use precise Exception such as
MeterDefinitionException.
This patch refactor all the DefinitionException classes.
Change-Id: I8147e593adf3a3213de165c6bbd118f882f00ab7
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
There is no reason to put EventFilter under metering storage
namespace, it is not common for the two storages. Let's move it
to the place it should be.
Change-Id: Ibf16e9b4bbf33fd2afe036dcfbd85d1d28e17c9d
|
|/
|
|
|
|
|
| |
If we use logging lib to initialize a logger, the logger won't be applied
the oslo_log config options.
Change-Id: Ib6bc686f4296cc335aa5abcc47f266a237d8688c
|
|
|
|
|
|
|
| |
oslo.utils has implemented a thread safe fnmatch, we can use it
instead of maintaining a private one.
Change-Id: Idb8a3d9f2b0fb16ec403f2da3ad00ee0d982454e
|
|
|
|
| |
Change-Id: I0718da0d8cd3a63708117d770b1bf21f9ce3bfe1
|
|
|
|
|
|
|
| |
It turns out the context object is never used by anybody, and is anyway
empty. So let's remove its usage completely.
Change-Id: I4efeb629dfd84e7cddeb0df908207cf017fc741c
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Race condition exists when 2 threads try to create same event_type, so
need detect it and load the event_type again.
Change-Id: If3439817cfbfef90daeb5975338909f8312864c4
Closes-Bug: #1254800
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
with timedelta plugin we could create new metric for latency time of
nstance booting without using events and its transformation.
we could define new meter in meters.yaml with volume as in example::
volume:
fields: [$.payload.created_at, $.payload.launched_at]
plugin: ‘timedelta’
as a result we get volume value equal to difference between two mentioned
timestamp fields in seconds.
Change-Id: If5084cc23212a0a6bd9dac8438d5d286f3415730
|
|
|
|
|
|
|
|
|
| |
This change uses the batch oslo.messaging listener
for the notification-agent but configures it have the same
behavior as the legacy one.
Change-Id: I460ab9dc387eb56108b5bceb7415c3ee6538bc54
Depends-On: I16184da24b8661aff7f4fba6196ecf33165f1a77
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Scan the source code and filter some results. Fix the typos in
the source code. Will deliver remaining results in other patches.
ceilometer/event/trait_plugins.py
Line 169: s/it's/its
/ceilometer/publisher/kafka_broker.py
Line 58: s/this option is/options are
Line 60: s/with with/with
devstack/plugin.sh
Line 400: s/the the/the
doc/source/install/manual.rst
Line 557: s/seperately/separately
Line 567: s/requirments/requirements
Change-Id: Ia4577724977ec255ad426c7c9647ac26d0280f24
|
|
|
|
|
|
|
|
|
| |
Now in event collection only ttl index existed, that means response
on queries for event collection will become slower with collection growth.
Additional indexes based on timestamp and event_type fields in improves this.
Closes-bug: #1526793
Change-Id: I87f13262a213828e1aca5fbe60544db78999a341
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
fnmatch is not thread safe for versions <= 2.7.9. We have used
it in some places without any lock for concurrency scenario. This patch
re-implements a thread safe match() which is very similar to fnmatch by
using its translate function.
Change-Id: I4b6c2ea72841201519144eb09ecf8c82b16b6143
ref: https://hg.python.org/cpython/rev/fe12c34c39eb
Closes-Bug: #1519767
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
oslo.db EngineFacade class only support options defined by oslo.db,
but we're passing options defined by ceilometer, so oslo.db complains
with a warning message:
NotSupportedWarning: Configuration option(s) ['alarm_connection', \
'alarm_history_time_to_live', 'db2nosql_resource_id_maxlen', \
'event_connection', 'event_time_to_live', 'metering_connection', \
'metering_time_to_live'] not supported exception.NotSupportedWarning
This patch makes sure only options defined by oslo.db will be sent
to EngineFacade
Change-Id: I2a39737a5f7824918c28ff2180f2ea95e7e82537
Closes-Bug: #1516515
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change continues to remove code duplication by factorizing the
yaml file loading.
This also homogenizes the error handling.
The precision of error message will be the same for all.
When the yaml file is incorrectly formatted, we now raise an exception,
instead of sometimes raising and sometimes loading an empty definitions,
that can generated an unwanted behavior of collector and notification agents.
Change-Id: I9ae8f519472f1ae2a14e61028a427ba6f3b0d1f3
|
|
|
|
|
|
|
|
|
|
|
| |
Currently we have three differents parts of code that parse samples
and notifications. All of them do the same thing.
The event one have some additionals feature "TraitPlugin".
This change removes the code duplication and allows to use TraitPlugin
into gnocchi and meter definitions.
Change-Id: Id125de92a5893d7afa5a3d55c3f183bd2035a733
|
|
|
|
|
|
|
|
|
|
|
|
| |
depending on sql driver, REPEATABLE READ isolation level may lock
an entire table and cause write timeouts. isolation level was set
originally to ensure consistent reads between 2 queries required to
build events. that said, we can avoid table locks by making
assumption that the 1st query is the correct base and any difference
given by 2nd query can be discarded.
Change-Id: Ic53e1addf38a4d5934b4e627c4c974c6db42517e
Closes-Bug: #1506717
|
|
|
|
|
|
|
|
|
|
| |
'split' plugin can be replaced by an jsonpath expresion
since jsonpath-rw-ext>=0.1.8.
This change deprecates it
Depends-On: I8cd971d6dd98cd6c4c3dc83696969c47e8cdd8ac
Change-Id: Iac2253c81dacaa1b2a2258569716d20916fc9920
|
|
|
|
|
|
| |
fix logging translation levels
Change-Id: Ie5386ad75c3803565280b5f8a08f8dd0366ac8dd
|
|
|
|
|
|
|
|
|
| |
When querying events with two different *request_id* trait filters, we
expect the response body is an empty, but it may be not. That is because
the multiple trait query filters are not combined correctly.
Change-Id: Id034b01cff891e928625bb0fa668c1ebd7dcf742
Closes-Bug: #1489062
|
|
|
|
|
|
|
|
|
| |
Pollsters and Post Sample implementation
will publish to the notifications.sample
queue with this change.
Change-Id: Iccb9261ee805d41ed057bd0ac72306cd6a2ddaff
Closes-Bug: #1484695
Closes-Bug: #1489341
|
|
|
|
|
|
|
|
|
|
|
|
| |
Acorrding the current event-list API, an admin user is allowed to query
all events which have traits.project_id value that match it's own project
OR any event without any project_id trait. In get_events() in
impl_sqlalchemy.py, this current query clause is implemented in a
inefficient way. This change make it more efficient.
Co-Authored-By: gordon chung<gord@live.ca>
Change-Id: I645a7def0552e2574da540e180b4f57d8770e96e
Closes-Bug: #1494440
|
|\ |
|