• Sole Purpose of Visit (unregistered)

    I'm sorry, but the distinction between an error logging tool and a crash reporting tool still completely eludes me. Other than the fact that the second one is (hopefully) a nice GUI wraparound to the first, with SQL queries and maybe a crude-to-sophisticated crash-stack-diff to group related failures ... I see nothing here.

    Still, nice advert.

  • beb (unregistered)

    If you're going to post an add that looks like a WTF entry at least identify it as such somewhere BEFORE the last couple of sentences.

  • X (unregistered)

    Wonder if Raygun is GDPR compliant... Not that it matters in the land of no privacy...

  • Zenith (unregistered)

    It's a people problem, not a technology problem. If your project is full of stupid people, no tool is going to make a bit of difference.

  • (nodebb)

    I've worked with eCommerce sites that display errors and ask users to contact the Help Desk over the most trivial of errors and even non-errors, like searching for things that aren't available for sale on the site. The user calls a Help Desk agent who records minimal, useless information ("User unable to place order" - place an order for what? What happened when they tried to place an order? Were they trying to place an order correctly, or did they speak into the mouse and say, '"Computer, place my order?")

    The Help Desk creates a ticket without asking any useful questions. They don't even know what time it happened. Their excuse is that they aren't developers and don't know what questions to ask. Every few years they ask the development team for a list of questions to ask, to which we would reply, "Ask the same questions we sent you last time you asked us that and then ignored us." The customer waits for a response that's never coming because the list of tickets is obviously huge and no one is going to call a customer a week later and ask them questions to which they can't possibly remember the answers.

    The company had a team of phone agents who could take orders, but the customers wouldn't call them and place their orders because we told them to call our Help Desk instead and talk to people who weren't going to help them, asked them the wrong questions, and told them to wait for a response which would never come.

    The solution I proposed and which was never implemented, was that we should log useful details of any exceptions because at the moment when those exceptions occur, our application knows more than a user could ever tell us. If the user can't place an order online, we should direct them straight to our phone agents, not to our Help Desk, because our Help Desk would already know about the problem. We should provide the user with a reference number that they can use if they want to call the Help Desk, (shoot, there's a character limit so I can

  • Dread (unregistered)

    If you're going to post an add that looks like a WTF entry at least identify it as such somewhere BEFORE the last couple of sentences.

  • (nodebb) in reply to Scott Hannen

    we should log useful details of any exceptions.... We should provide the user with a reference number....

    We're implementing exactly this. It makes a lot of sense.

  • Ruts (unregistered)

    Looks like an advert to me. Is the real WTF that this is essentially spam, dressed up as a technical WTF

  • Diane B (unregistered)

    When I'm coding I drink Diet Coke!

Leave a comment on “Error Logging vs. Crash Reporting”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article