InfluxDB vs. Sentry

InfluxDB is very good at storing monitoring metrics (e.g. performance data). InfluxDB is not the right choice if you need to store other data types (like plain text, data relations etc.).

Incentivized

Great for standard web application performance monitoring, analytics and error reporting. Shows line level code errors, gives insight into performance issues (plugins, API issues, etc.). Automation and scheduled scanning in production gives client visibility into 'after deployment' value. Also lets a relatively small number of developers keep tabs on a handful of different site/applications without needing a bunch of tools. The UI is pretty complicated and can be overwhelming for new users. Documentation could be better for the learning curve,

Incentivized

• Perfect handling telemetry data.
• Low latency, near real time.
• SQL-like language makes it easier to query.

Incentivized

• Great web interface. Lots of data available in a really clean format, with filtering options and more.
• Per-user exception tracking. User is complaining about something being broken? Look up their account ID in Sentry and you can see if they've run into any exceptions (with device information included, of course).
• Source map uploading. Took a little while to figure this out but now we have our deploy script upload sourcemaps to Sentry on each deployment, meaning we get to see stack traces that aren't obfuscated!
• Very generous free tier – 10,000 events per month. We're nowhere near that yet.

Incentivized

• GUI based administrator console

Incentivized

• Alert Configuration. Would be really helpful to have multiple logical groupings within the "If" section of a single configurable alert.
• Alert Copying. Being able to copy an alert from one project to another would be super beneficial.
• Alert Tags. Better UI around how we select which tags are getting sent with each alert instead of a tiny text box.

Incentivized

InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.

Incentivized

Its incredibly versatile, but that leads to complexity for the uninitiated, which can be intimidating. Nevertheless its a well polished product, in our case leading to only using it for a focus on frontend is still more cost effective than buying a one-to-rule-them-all tool...

Incentivized

We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.

Incentivized

To be honest, I didn't look at alternatives since InfluxDB performs very well if you can oversee the lack of security and HA features. But for all challenges, there is an easy solution which brings you forward (e.g. read load balancing can be achieved by using a common HTTPS load balancer).

Incentivized

It is cheaper and offers better support for front-end applications for enterprise large environments with more then 30 scrum teams and hundreds of micro frontend applications. The configuration options, both with the agent and from the user interface, are superior to other tools, and the documentation is also very easy to use.

Incentivized

• Provided us a time series DB.
• With the SQL-like language, it is very easy to learn.
• Empowered us to keep track of our events.

Incentivized

• So it has helped us for quick error resolutions.
• From dashboard we are able to assign errors to particular member and see when its resolved.
• Without customer informing us about errors we know what happened in real time helps in customer service also.

Incentivized