"Scout Does Things Right": Gigmit on using Scout

April 26 Bullet_white By Nick Bullet_white Comments Comments

Benjamin Knofe of Gigmit

Benjamin Knofe, CTO of Gigmit, sat down with us to share how they use Scout to improve their performance.

What is Gigmit?

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.

How big is your userbase?

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.

How large is your dev team?

We have a team of 5.

Tell us a bit about your app's infrastructure:

Our stack includes DigitalOcean, Ubuntu, nginx, Unicorn, Rails, Postgres, Redis, Elasticsearch, Amazon S3, and Sidekiq.

What are your monitoring tools?

On a regular basis we use Scout, New Relic (free), Logentries, and some custom in-house monitors.

What was your biggest hesitancy before using Scout for app monitoring?

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.

What did you use before Scout for app monitoring?

New Relic pro.

Why do you use Scout for app monitoring?

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.

Get notified of new posts.

Once a month, we'll deliver a finely-curated selection of optimization tips to your inbox.

Comments

comments powered by Disqus