Squash: The open-source bug-smashing tool Error Monitoring, Error Tracking, and Notification for Ruby on Rails 2, 3 and 4 - Honeybadger LESS « The Dynamic Stylesheet language Track Errors with Google Analytics Google Analytics has always been more than a hit counter and demographic tool -- you could build a career out of being a Google Analytics analyst. You can measure ad campaign effectiveness, track how far into a desired page flow (think advertisement to cart to checkout) users get, and set browser and locale support based your user's information. But that's all stuff for the suits, not us devs. What us nerds can use Google Analytics for, however, is error tracking via custom events. Here's a quick look at how I've implemented error checking in analytics: Now when you go into Google Analytics, you can view the custom event information along with other site stats.
Vert.x 3 MongoDB Conf The client is configured with a json object. The following configuration is supported by the mongo client: db_name Name of the database in the mongoDB instance to use. useObjectId Toggle this option to support persisting and retrieving ObjectId’s as strings. The mongo client tries to support most options that are allowed by the driver. connection_string The connection string the driver uses to create the client. Specific driver configuration options Driver option descriptions host The host the mongoDB instance is running. port The port the mongoDB instance is listening on. hosts An array representing the hosts and ports to support a mongoDB cluster (sharding / replication) A host in the cluster The port a host in the cluster is listening on replicaSet The name of the replica set, if the mongoDB instance is a member of a replica set maxPoolSize The maximum number of connections in the connection pool. minPoolSize The minimum number of connections in the connection pool. maxIdleTimeMS maxLifeTimeMS
errbit/errbit Lighthouse - Beautifully Simple Issue Tracking Why choose a plan when you're not sure how you'll use Lighthouse? Check out our offering now and after 14 days you can choose the plan that fits you best or stick with the free plan and you won't be charged a dime! Top-Shelf Offering GOLD$100/month Unlimited projects Unlimited members 50GB of file storage Priority state for projects For Larger Companies SILVER$50/month 20 projects 50 members 10GB of file storage Priority state for projects Perfect for Startups BRONZE$25/month 10 projects 15 members 2GB of file space Priority state for projects Save 10% by signing up for a year in advance.
Nerdery Interactive Labs | Web Development Partners for Creative Agencies, A Division of Sierra Bravo Corporation An Easy Javascript Error Logger using Google Analytics If your site contains any sort of non-trivial Javascript, logging client-side errors can no longer be considered a luxury. We’ll explore a free method to start logging exceptions with just a few lines of code. Because there’s so many different browsers and configurations out there it’s much harder to write Javascript that works flawlessly everywhere compared to for example server-side code, and you already probably log server-side exceptions. Graphing the amount of errors happening There are many services out there that allow you to log client-side exceptions, but naturally none of them are free once you go beyond the basic offering. Luckily Google Analytics is still free, and we can easily feed it our errors as events. How To We’re going to create a Google Analytics Event every time an exception happens. _gaq.push(['_trackEvent', category, action, label]) To catch the exceptions, we’ll use the window.onerror event handler, which gives us the file, line-number and actual exception message.
Undertow, Vert.x, and Netty Benchmarks - Miles to go 2.0 ... 90 frameworks (including web application platforms, full-stack frameworks, and micro-frameworks) are compared using 230 tests by Tech Empower. The tests execute fundamental tasks such as JSON serialization, database access, and server-side template composition. Read more about the tests introduction, permutation, and environment details. Complete results from Round 8 are explained here. Undertow is the new web server in WildFly 8 and did pretty well with consistently staying in top 10 in all categories, especially given that the server is written from scratch. Vert.x and Netty – two more frameworks from Red Hat are doing pretty well too! Here is a snapshot of some of the results: Top 3 frameworks here are by Red Hat WildFly 8 was recently released and uses Undertow as the web server.
Exceptional: an exception tracker for web apps The Trac Project The Fine Art of JavaScript Error Tracking – Medium Things I Learned Signal vs. Noise There was a common theme among the cons of all the services I looked into: noise. I knew dealing with JavaScript errors was messy, but I didn’t realize just how difficult it was until I dove into it. The stark reality is that the noise is not going away any time soon. The State of Stack Traces Everyone knows JavaScript stack traces blow, but this fact really gets hammered in when you’re sifting through dozens of them in desperate hope of direction. How We Use Sentry Reporting Our JavaScript Sentry projects are set up to correspond to entire pages on our site that might contain one or more small Angular apps. Identification Sentry is pretty great at surfacing important JavaScript exceptions. We look for the spikes in the stream. Let’s dive into the cryptic, vague [object Event] exception. As you can see, this is one of the more useless error messages. Sometimes we’ll come across errors with nearly zero context from which we can try to reproduce them.