Disable scheduled usage ping generation in .com
Opening this as a follow up for this discussion !49559 (comment 464935610)
cc @nick.thomas
Usage ping generation is not currently working in gitlab.com
Sidekiq job is killed as the generation takes more than 33 hours
We could disable the generation and not add extra work if we know is always going to fail.
If we decide to go with a no sql metrics version of usage ping we could keep the scheduled job
cc @gitlab-org/growth/product_analytics/engineers
Edited by Alina Mihaila