The contents of this repository are still available in the Git source
code management system. To see the contents of this repository before it
reached its end of life, please check out the previous commit with
"git checkout HEAD^1".
For any further questions, please email
openstack-discuss@lists.openstack.org or join #openstack-telemetry on OFTC.
Change-Id: Ic8a7001e708d8da7cf8951eefd0a96762ea5fa46
When thare're a lot of events in the database panko-expire
consumes a lot of memory to delete all records with a single
call. To avoid this behaviour a new config option
`events_delete_batch_size` was introduced.
Change-Id: Icf83ffe089301b3782273923f18efd4d209131c2
Configuration options must be registered before using them.
In impl_elasticsearch.py, using conf.database.es_index_name
or using conf.database.es_index_name are all wrong that will
lead the api server to be invalid.
Change-Id: I6b1364954c231a477d493d4a518c080f87058123
Signed-off-by: yuanrunsen <yuanrunsen@unitedstack.com>
currently when there is a problem with configuration, the logging is
insufficient, especially when running panko-dbsync command.
Change-Id: I22ef74eb45f324fc6e374c4a3e03fbe9d7268eed
- we don't need to prefix 'event/storage' because that's all panko
does. cleanup inline with aodh.
- test_hbase_table_utils is not used anywhere and last reference
was from icehouse.
- drop a few places that use 'event_*' prefix since it wastes line
space
Change-Id: I348f5a3dfb59682589b4912eaed4e4b8abb15ebb
sorting and marker options are enabled for event listing (for sqlalchemy only)
using oslob.db.
sort -- list of sorting criteria. Each sorting option has to format
<sort key>:<sort direction>
Valid sort keys: message_id, generated
Valid sort directions: asc (ascending), desc (descending)
This defaults to asc if unspecified
If sort list is unspecified, this defaults to
['generated:asc', 'message_id:asc']
marker -- If specified, assumed to be an integer and assumed to be the
message id of the last object on the previous page of the results
limit is still available and supported for non sqlalchemy databases
Closes-bug: #1615699
Change-Id: I0441ca6283be5859c09c3d381ffbb52ca4a79eca
Matthias Runge