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
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: Ie6e22b0b47c5148290f7b76c95967cd9a343343c
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Update local hacking checks to work with new flake8 version.
Change-Id: Id5d224358b44fd7ab4bd3d08f1db6b6faf54042f
oslo project provide jsonutils, the others project use it
this PS to update the json moudule to oslo jsonutils.
Change-Id: I311d4f9dec7b685a5bccb9725de6010926375c7d
* Add osprofiler wsgi middleware. This middleware is used for 2 things:
1) It checks that person who wants to trace is trusted and knows
secret HMAC key.
2) It starts tracing in case of proper trace headers
and adds first wsgi trace point, with info about HTTP request
* Traces HTTP API calls
* Traces DB (SQLAlchemy) calls
Demo: https://tovin07.github.io/panko/openstack-event-list.html
HOW TO TEST?
1. Install devstack with panko as usual
2. Install osprofiler
pip install osprofiler
3. Add these line to /etc/panko/panko.conf
[profiler]
enabled = true
hmac_keys = SECRET_KEY
connection_string = redis://localhost:6379 # example when using redis
4. Pass HMAC_KEYS to client commands
- panko client with `--profile <HMAC_KEYS>`
- openstack client with `--os-profiler <HMAC_KEYS>`
Output will look like this:
To display trace use the command:
osprofiler trace show --html <TRACE_ID>
5. Use osprofiler to get the trace
osprofiler trace show \
--connection-string redis://localhost:6379 \
--out out.html \
--html <TRACE_ID>
6. Open that html file with browser and view the result
Change-Id: Ic934acbe1340a3e00361f2709f34725e0e4aa3ba
This reverts commit b540674a84.
This changes is wrong in the sense as it removes the ability to filter via ge/le the start and end timestamps.
Change-Id: I0c82917a6fd6795266e34b4d151faf13f43ab5bb
This is part of a community effort to provide better user experience
for those having to maintain RBAC policy. More information on this
effort can be found below:
https://governance.openstack.org/tc/goals/queens/policy-in-code.html
bp policy-and-docs-in-code
Co-authored-By: Hieu LE <hieulq@vn.fujitsu.com>
Change-Id: I9bad70abcf5543c3e5e5da25c56c408ee3ff0346
Currently admin can only get project_id consistent events, while
sometimes admin need to get all the events, so add a parameter
"all_tenants" for the api to achieve this purpose.
Change-Id: I7c479a63c41d4b0fbf645bdb1b70f0259b0cb859
start/end_timestamp originally are associated with op 'ge' and 'le'.
Changing them to 'eq' fixes the bug and the usage will make more sense.
Related review: https://review.openstack.org/#/c/495763
Change-Id: Ia94a499f9340102553863db48dccb96bea92ea78
Closes-Bug: #1711997
It was not documented how to filter based on `generated` field.
Added a field and a description for it so that it gets rendered in the
docs.
Change-Id: I3f4929ce4876015817e230d8855dbccbd5d34e27
- 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
Openstack common has a wrapper for generating uuids. We should
use that function when generating uuids for consistency.
Change-Id: I839aef8095960ebe00e6e7992c5415b7d7dfa3d9
Closes-Bug: #1082248
The Log "LOG.error(_LE(...)" is used in some places,but
the log "LOG.error(_(..))" still used in a few places.
Change-Id: I624d1f8dd770ff9802cfa0b0c56cf0501aa1a0fc
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
Currently, the query is checked against the `eq' operator, which is
wrong. The SQLAlchemy driver code only implements one operator, which is
gt/ge/eq depending on the field. This patches fixes that correctly in
the API.
(cherry-pick from commit 36df404e4202a821110e19bc8db554120ea1b7ae from Ceilometer)
Change-Id: Ife02ef6166902120f5e10103d73bb009713cb3bf
Matthias Runge