Reviewing event usage due to sudden billing limit
We just noticed 402 errors. It's pretty perplexing because we don't have nearly enough users to trigger this and the amount of activities is less than 1000 for the billing period so far.
I don't know if we have an API key leaked or if development environments are being counted etc.
Is there a way to get some visibility? We're worried if we pay the increased tier cost we'll just end up blowing through it anyway.
12 Replies
Our environmentID is
65113f461a7614493dc5a9f6Hi @πππ§π€ π let me loop in @Pawan Jain to ensure we resolve that.
@πππ§π€
Thanks for reaching out and sharing environment Id.
As per logs, your organization was upgraded to business tier on
12 Dec 2024, 03:00 UTC time
Before this, your account was in free tier and only 30k events per month are included in free tier.
Looks like your organization tried to send more than 30k events per month in free tier.
Checkout our pricing page and rate limiting policy for each tier
Since you have upgraded to business tier, you should not get 422 errors if requests are as per business tier rate limit and quota limit policyYea my concern is trying to get a more granular view of why I suddenly got those events. Is there a way for me to see a breakdown of events per day/week? I've rotated api keys in case there was a key leak
I dont want to end up blowing through the business plan because of a deficiency in our setup that I want to try and isolate
Activities feed page can be used to check the events triggered on a specific day
https://dashboard.novu.co/activities
Novu Cloud Dashboard
Novu Cloud Dashboard
79k+ events were triggered on Monday 9th Dec which consumed whole 30K free quota
ok thanks, just a few questions so I can appease my overlords.
How do dev and production environments account for billing? are dev environments also included?
And on the topic of events, I see in the docs:
A trigger event is a request that initiates a process in Novu's logic engine (like an API call to /v1/events/trigger). Each trigger event can perform multiple actions including digests, delays, and sending notifications across various channels, as well as filters and user preference checks. Billing is based on trigger events that start a process in the logic engine for each unique subscriber.Would a trigger event sent to a topic that contains say 100 subscribers be considered 100 events? I've tried to ask the AI in docs btw and it doesn't appear to know the answer
How do dev and production environments account for billing? are dev environments also included?Yes, total events counted in billing is sum of both development and production environment
Would a trigger event sent to a topic that contains say 100 subscribers be considered 100 events?Yes, it will be counted as 100 events
Thanks, I think it's worth highlighting this in the docs.
@πππ§π€, you just advanced to level 1!
Hey folks, just a final thing to add. We didn't receive any notifications that this was happening. We only discovered it after we noticed an increase in our own logged errors.
Such a drastic increase in volume should trigger something and if not that, at least a notification that we surpassed our event limits.
Hi @πππ§π€, agreed! Iβll let me pass it to the team, and ensure we are adding something like that π