Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scalelite Recordings Metrics & BBB Exporter #545

Closed
faust64 opened this issue May 10, 2021 · 3 comments
Closed

Scalelite Recordings Metrics & BBB Exporter #545

faust64 opened this issue May 10, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@faust64
Copy link
Contributor

faust64 commented May 10, 2021

Hi,

Deploying Scalelite and the BigBlueButton Exporter ( https://github.com/greenstatic/bigbluebutton-exporter/ ), I noticed that while that exporter reports the right values for recordings (published / unpublished / update / deleted) when querying my BigBlueButton servers API, it seems to be broken when querying Scalelite.

The counters for published / unpublished / update / deleted recordings are all equals to the same value, which is the count of published recordings.

AFAIU, the exporter would query for some getRecordings API call, passing an argument ("deleted", "published", ...), over there:
https://github.com/greenstatic/bigbluebutton-exporter/blob/master/bbb-exporter/collector.py#L202

The recording state being sent as a param, in getRecording API command:
https://github.com/greenstatic/bigbluebutton-exporter/blob/master/bbb-exporter/api_lib.py#L86

Now, AFAIU, Scalelite doesn't look for arguments in the getRecordings command:

Thus, when the exporter would query for getRecordings with different arguments, the same counter would be returned 4 times.

I think it could be fixed with something like this:
https://github.com/blindsidenetworks/scalelite/compare/master...Worteks:fix-recordings-metrics?expand=1

After a few tests, I think this works - at least, I only see my published records (don't have others, and can't really test delete stuff/testing against prod...). PR is on its way ...

@jfederico
Copy link
Member

Yeah, I don't think that filter was ever implemented in SL. This could be an enhancement

@jfederico jfederico added the enhancement New feature or request label May 10, 2021
@faust64
Copy link
Contributor Author

faust64 commented May 10, 2021

I've ended up upgrading my setup, building my own API image, and bumping the recordings-importer/poller/... to 1.1-beta.4.
See #546

Looks like it works. Though I'm no ruby nor BBB expert ...

@git-lama
Copy link
Contributor

closed by pr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants