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

✨ Add metrics endpoint #389

Merged
merged 4 commits into from
Nov 27, 2023
Merged

✨ Add metrics endpoint #389

merged 4 commits into from
Nov 27, 2023

Conversation

pajowu
Copy link
Member

@pajowu pajowu commented Nov 17, 2023

No description provided.

@pajowu pajowu requested review from anuejn, phlmn and rroohhh November 17, 2023 23:46
@pajowu pajowu force-pushed the pajowu/metrics_api branch from 26c441f to 08b567d Compare November 18, 2023 22:39
@pajowu pajowu marked this pull request as ready for review November 18, 2023 22:39
@pajowu pajowu force-pushed the pajowu/metrics_api branch 4 times, most recently from 8bed38d to 0472589 Compare November 19, 2023 22:05
pass


class TasksInState(Metric):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather like to have this as TaskChanis or TaskGraphs in state. Otherwise this number is not really saying much (Transcode is much faster, yadayada)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the nicer way would be to have the task type as a label as well, I'll change that

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer some other task parameters (that influence needed computing time) as labels then too


class Queue(Metric):
def __init__(self):
self.collector = Gauge("queue", "Queue length in seconds")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here. I would like to have every task chain only counted once

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or maybe we introduce some unit here that is not seconds (maybe something like estimated compute seconds on some specific platform? the mac mini?)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes and no. Doing a better calculation that takes into account the real time factor of different machines etc would be a nice addition, but I'd rather do that in a seperate PR, as this has some more open questions to me (and probably needs some database changes as well)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then for the time being only count transcription tasks?

@pajowu pajowu force-pushed the pajowu/metrics_api branch from 82b6463 to 8db05ec Compare November 21, 2023 10:57
@pajowu pajowu requested a review from anuejn November 21, 2023 11:28
@pajowu pajowu enabled auto-merge November 27, 2023 20:05
@pajowu pajowu disabled auto-merge November 27, 2023 20:07
@pajowu pajowu added this pull request to the merge queue Nov 27, 2023
Merged via the queue into main with commit 5270089 Nov 27, 2023
2 checks passed
@pajowu pajowu deleted the pajowu/metrics_api branch November 27, 2023 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants