El uso: cómo Intelligence Fusion implementa Sentry
Intelligence Fusion uses Sentry for error monitoring and, more recently, performance monitoring, tracing and profiling across its PHP, Go and TypeScript services. The engineering team uses it to find and fix slow endpoints and database queries in its threat intelligence platform and REST APIs.
Otros resultados publicados
Cifras publicadas en el caso de estudio de Sentry. usedby no las mide de forma independiente.
API 1 (threat actors) average latency decreased from 1820ms to 23.8ms
API 2 (static assets) average latency decreased from 60.7ms to 24.1ms
API 3 (authorization) average latency decreased from 105ms to 24.9ms
Ultimately, average time decreased from 17.5 seconds to 1.2 seconds – making their API response time 13x faster.
En palabras del cliente
Sentry has always been our go to tool for critical error handling to ensure we continue to deliver reliable and robust software. As Sentry has evolved its offering, it has allowed us to not only scale our microservice architecture horizontally but vertically, as Profiling and performance metrics let us dive deeper into our applications to ensure we provide an optimal level of performance for our customers.Otras empresas que utilizan Sentry
Clientes de distintos sectores, con pruebas públicas.
Animation Digital NetworkConfirmado
AnthropicConfirmado
ArcadeConfirmado
AtlassianConfirmado
BasetenConfirmado
BitnamiConfirmadoConsultar la fuente
Basado en el caso de éxito publicado por Sentry. Verificamos las pruebas públicas; los resultados son los que declara el proveedor.
sentry.io- Última verificación
- 13 nov 2026
Abrir la captura Lo que dice la historia, y lo que verificamos
Lo que comparamos con la página.
- La cifra: 13xVerificado
Impresa palabra por palabra en la página, cerca del nombre de Intelligence Fusion.
- El pasaje citado arribaVerificado
Copiado palabra por palabra de la página, cerca del nombre de Intelligence Fusion.
- Intelligence Fusion usa SentryVerificado
Línea de nivel Confirmado.
- El resultado en síNo verificado
Lo citamos; no lo medimos.
The slowest endpoint, their country data endpoint, initially took 17.5 seconds to return. Having identified the database query as the biggest bottleneck from the flame graph, they optimized the endpoint in several ways