April 26, 2016
Benjamin Knofe, CTO of Gigmit, sat down with us to share how they use Scout to improve their performance.
Gigmit is a platform to connect music professionals to one another. Artists get opportunities to play gigs, shows, and festivals all over the world by showcasing their music and applying for gig listings created by promoters.
We support 30,000 artists and 2,500 promoters world-wide. We also offer a suite of tools for all things involved in live event management: booking, merchandise, ticketing, and promotions.
We have a team of 5.
Our stack includes DigitalOcean, Ubuntu, nginx, Unicorn, Rails, Postgres, Redis, Elasticsearch, Amazon S3, and Sidekiq.
On a regular basis we use Scout, New Relic (free), Logentries, and some custom in-house monitors.
Scout was still new and in development, and lacking some features we were used to seeing elsewhere. Because Scout can be deployed side-by-side with our other tools, it's not an issue.
New Relic pro.
Scout does things right, New Relic messed up. Our goal was simply to find bottlenecks in our app and fix them. With the help of Scout, we're good to go.