As a software developer, you know that your code is only as good as your information. Whether you’re fixing a bug, assisting a user or designing a new feature, you don’t want to be working on the basis of incomplete information. That’s why you set up systems that report back to you: analytics, console statements, server logs, status reports, code breakpoints, et cetera. But there’s one critical component of your product that’s not reporting to you, and should be: your user’s browser.
That’s what Hawk does: our code snippet lives on your front end and sends back information about errors and user behavior, so you can get an over-the-shoulder look at what’s really going on when your application runs.
This week, we’ve added some features to help ensure your users’ security, paint a clearer picture of their experience and integrate more completely with the workflow you already have in place:
Security: Sensitive Data Masking
Your users’ private data needs to stay private. The Sensitive Data feature lets you ensure that Hawk never reveals what it shouldn’t. Tell us how to identify network traffic or DOM elements containing sensitive data, and Hawk will responsibly mask it before transmitting anything.
For more information on how to use this feature, see here, and for a list of the data we hide by default, see here.
Analytics: User Identification
You can’t help a user if you don’t know who they are! Let us take the detective work out of identifying which user you’re looking at. Use our robust network traffic filters to point out what server responses contain identifying data, and we’ll be able to track your users across multiple sessions and devices, creating a coherent picture of that unique individual’s interaction with your site. For more information on how to set up user identification, see here.
Analytics: Error Filtering
Looking at a list of every error your site produces can be like drinking from a firehose–it’s just too much to digest. That’s why we’ve built robust filtering into Hawk. Choose from a huge number of possible criteria and drill down to exactly what you’re looking for. For more details on error filtering, see here.
Analytics: Ignore & Resolve Errors
As developers, we understand that an error does not always represent a bug. Whether because of your project’s idiosyncrasies, a library you’re using or an external resource you interact with, sometimes error messages just don’t mean anything. If that’s the case, let us know by marking it Not a Bug and we won’t bother you with it anymore. You can also mark an error report Fixed; in that case, we won’t show it to you anymore unless it happens again.
Workflow: Slack Integration
When a user encounters a serious bug on your site, they usually don’t tell you about it; they’ll try to get around it, and then they’ll move on. What if, when that happened, you got a message on your Slack board?
That’s exactly what our Slack integration feature does: it sends error reports generated on your website to your Slack board, complete with analytics and a screenshot. It’s like giving your website the ability to voice its own concerns and complaints: Nobody has to go and check what’s going on with the site–it’ll tell you itself.
For more information about our Slack integration, see here.
See Hawk on the Slack App Directory here.