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

TrackJS use is out of quota #14890

Closed
2 tasks done
VictorVelarde opened this issue May 15, 2019 · 2 comments
Closed
2 tasks done

TrackJS use is out of quota #14890

VictorVelarde opened this issue May 15, 2019 · 2 comments
Assignees

Comments

@VictorVelarde
Copy link
Contributor

VictorVelarde commented May 15, 2019

Context

We currently have a license to use TrackJS for JS errors. The 'applications' registered in that tool are:

  • Builder
  • Builder embed
  • CartoDB central
  • CartoDB editor
  • CartoDB embeds
  • CartoJS

It is a really useful tool, but now we need to make some changes in how we use it.

Current

Our limits are set for 10 million page views (with 15 days retention), but we have run several months out of that quota, as TrackJS people have gently notified us.

This TrackJS dashboard displays our metrics: https://my.trackjs.com/usage (requires FrontEnd credentials)

So now we need to take some action on it.

We were offered an upgrade to the next level (25 million page views), but after discussing it internally, we have finally decided to reduce our use, so we can fit into the current plan.

That's mainly because of 2 reasons:

  • the apps are pretty stable now
  • most of the quota is consumed by 'embeds' (>=80%), and we think we can reduce safely that 'noise'

For example during the last 2 weeks:

  • 6.6 million page views
    • Builder embed: 4 million
    • CartoDB embeds: 2.5 million

Expected result

We must take some actions to we fit into the current paid plan.

We should conditionally include the library in the embeds, so we lower its page views number. For the very nature of those embeds, we think we can safely reduce the inclusion to just a 20%. Discarding the other 80% would for sure make us fit into the plan, but without losing relevant issues.

The other task is having a quick review of the noise / signal ratio in other apps, to see if we can improve there.

So, to sum up:

  • Reduce the use in embeds:

    • Builder embed
    • CartoDB embeds
  • Quick review of TrackJS at:

    • Builder
    • CartoDB central
    • CartoDB editor
    • CartoJS

Additional info

I'm gonna notify TrackJS people that we are working actively on this, by sharing the link to this issue.

@VictorVelarde
Copy link
Contributor Author

Please, @CartoDB/rt-managers add this to RT, so we can start working on it asap

@VictorVelarde
Copy link
Contributor Author

For the first time in some months, in June (2019) we're under quota limits again. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants