-
-
Notifications
You must be signed in to change notification settings - Fork 732
v3: usage tracking #1163
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
v3: usage tracking #1163
Conversation
|
I think "Micro" should be renamed "extra-small-1x". "Micro" feels hard to place as a size and doesn't fit with the pattern which is nice other than this. |
731aebd
to
c05d958
Compare
.setIssuedAt() | ||
.setIssuer("https://id.trigger.dev") | ||
.setAudience("https://api.trigger.dev") | ||
.setExpirationTime("2h") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if some a task is still executing after 2 hours?
We need to support refreshing the JWT tokens because some runs last longer than a day |
…ing that via otel and to completed task run attempts
95e1bb8
to
9523366
Compare
In preparation for adding billing support for the v3 cloud, this PR introduces the tracking of run usage, and changes the machine configuration to use preset names instead of any combination of CPU/Memory.
Machine presets:
You can also now configure a default machine in trigger.config.ts.