Shockey Monkey

RIP: banana.shockeymonkey.com

I figured banana.shockeymonkey.com deserved a public funeral for all the good stuff it brought to the community. Banana was the server that was used as the primary development/test platform for Shockey Monkey from 03/2006 to 08/2006 and it really made this wonderful project possible.

The server ran continuously without reboot since 03/2006 and was about as rock-solid of a platform for a standalone server as one can imagine. It was shut down finally around 9 PM earlier tonight.

Shockey Monkey Popup Error

I fixed a slight issue with Shockey Monkey this morning that affected customers using Internet Explorer 6.0 SP2 and below. One of the AJAX libraries apparently was making references to HTTP objects and customers with older browsers got the following message:

This site contains both secure and insecure data. Do you wish to display the insecure data?

The issue did not affect the newer browsers (Internet Explorer 7, Firefox 2) and has been fixed this earlier this morning and should work just fine now. As I mentioned, it might take maybe a week to hammer out the AJAX implementation and adjust the interface in the way it makes sense and makes people more productive.

I want to thank Amy Babinchak, Daryl Maunder, Bill Waters, Mark Gravell, Jeff Altman and Manny Oliva for taking time out on a busy Monday morning to help me get to the bottom of this and fix it right away..

Shockey Monkey AJAX Upgrade, Changelog, Roadmap

As mentioned last night, I’ve put in a significant amount of effort into adjusting the interface to make people more productive with Shockey Monkey. Big part of that is a technology known as AJAX (for the most part its actually AJAH with very little XML) which allows me to update page elements without forcing you to load another page, popup another window, etc.

Upgrade Changelog

  • Rearranged ticket update interface. Information that is often updated (now including priority/escalation) is visible by default; To add extra information such as time and billing you can click on text to slide in a time entry panel.
  • Bumped up comment field for ticket updates to 80 colums. The new field allows you to see more of your ticket update as you are typing it in.
  • Added ability to insert both public (client visible) update as well as internal notes (private company / staff) update on a single ticket update. This is useful if you are updating ticket with additional information that you may not want to disclose to the customer.
  • Ticket display now supports filtering by company name (per popuar request). By default the Support tab will show all open tickets in the system, selecting a company under "Show tickets for" dropdown applies a filter and displays only tickets for the selected company. This value is persistent, meaning that it will filter across closed, urgent, new and assigned to me support requests. To show all ticket requests just adjust the filter to "All"
  • Updated color scheme to reduce puke-orange feeling you get while reviewing a request. While I did enjoy the contrast the orange brought to the blue site, anything that can be done to place the monkey in the stage of melancholy where they don't become smartasses with the clients is good in my book. CSS will eventually be completely customizable.
  • AJAXified ticket listings so you can pan (or over) over the first column in the ticket row display and see last three ticket updates to the ticket without clicking on it. The details presented are users name, time of update as well as full text of update comments.
  • AJAXified ticket view screen to allow you to edit the subject of the ticket in case your customer provides a stupid/misleading ticket subject (as per Daryl M.); Hover over the ticket subject on the ticket view screen and double click on the subject. Input box will appear.
  • AJAXified new contact creation screen, the company field now supports autocomplete. Autocomplete is similar to intellisense technology on your PocketPC or for those of you familiar with Visual Studio, after the second character is entered it will run an AJAX search and display companies with similar names. This is to address an issue where staff members keep on creating accounts for users from the same company but with slight nuances in the company name listing, which then creates a separate company account and splits information. This autocomplete will hopefully let the user know if a similar company is already in the system.
  • AJAXified the search control. Much like the company autocomplete, the search bar will now run an AJAX search against users and companies in the database and give user an option. This is a PARTIAL search, it will match anything in the name, so if you're looking for a company that you remember having "Tek" in it, the AJAX search will match "AsusTek", "SmartTek", "AvanTekNoligies", "TekGuy LLC" and so on.
  • Updated SmartPhone application (/m.asp) to include ability to update priority and status on ticket update. Also added ability to add billable time (number of minutes worked)
  • Updated SmartPhone application to support "Signout" and "Recent Updates" functionality. Recent Updates only shows tickets that have been updated since the last login or signout event. Signing out of the application only stamps the session as having ended, because the login information is passed in the header you do not have to log back in when you access the application again. This is done by design because it can take a while to login to an application using the phone.
  • SmartPhone application now also supports time zone adjustments.
  • SmartPhone application now displays the corporate logo when accessed. I have no excuse, I was bored and this seemed easier than whatever other problem I was trying to solve at a time.
  • Updated Roadmap

    I’ve made it no secret that I have wiped off my entire schedule for the second half of 2007. There are a lot of reasons for that but this is a major part: I am committed to delivering the whole platform by the end of September, roughly a year after Shockey Monkey launched as a helpdesk app. As you can tell from the roadmap, the next two months call for the integration of already stable WMI agent code, documentation and accounting modules as well as some extra management stuff.

    July 13
    - Finalized VoIP integration for TrixBox
    - Finalized mail code for alerts, inbound mail, ticket generation
    - Finalized AJAX interface

    July 20
    - Dispatch manager (geopositioning, Google Maps, directions and schedules)
    - Support routing and SLA Manager (for example, autoescalate tickets after X hours without a touch)
    - Shockey Monkey Mobile (WM5 Application)

    July 27
    - Finalized Documentation panel (for documents and forms such as network information, server information, ISP configuration, routing, accounts)
    - Shockey Monkey WMI Agent

    August 3
    - Bug fix/check week

    August
    - Accounting integration work with GP, Office Accounting, Quickbooks
    - Possibly an Outlook plugin but no promises

    This leaves September for bug-fix work, October for reporting and finally November for commercial launch along with a virtual machine shipment so you can deploy Shockey Monkey in your own enterprise environment, on your hardware, behind your firewalls, etc. Basically, addressing 100% of the initial needs of the project when it was first put together.

    Shockey Monkey AJAX upgrade preview (release tomorrow)

    So for the past two weeks I have been working on the general interface improvement of Shockey Monkey. Here are a few features that are seeing their first light of day mostly due to the demands of my staff, I hope the Shockey Monkey users consider them and we find a way to make them available throughout the interface without absolutely destroying the app.

    I am the most prolific and vocal hater of CRM software, in my 28 years on this planet I have yet to see one that I like. So Shockey Monkey is as anti-CRM as I can possibly make it. Today, I am close to that goal – 0 popup windows. Thats right, 0 popup windows. That presents a challenge in presenting information so let me give you a bit of a preview of how I’m addressing that. By the way, all screenshots are thumbnails so just click on it to enlarge.

    Intelligent Tips

    Perhaps the most powerful part of AJAX is the intelligent tooltip float. Shown below for the ticket display module (also works in the accounting ticket display) it shows you last 3 ticket updates along with names and timestamps as you hover over the ticket line. You don’t have to click on anything, you don’t have a popup window to dismiss, you just have to hover over the little icon and it will dynamically load the data from the database.

    Why is this significant? We have trouble prioritizing. Clicking on tickets, opening them one by one whether directly or by sending them to a new tab is just a waste of time and a lot of mouse / keyboard coordination comes into play. This little tweak allows you to see the latest ticket updates and prioritize your response – attack whatever is the most urgent – Was the last customer response “Ok, great, that works now!” or was it “If you don’t fix this today we’re looking for a new company!”

    Sm-preview1

    And yes, Daryl, that is the feature you requested – Company filter as close as I could get it to what you guys described you liked about Kaseya. Dropdown allows you to filter tickets by company. Haven’t had to use this but it seemed to be popular with the crowd.

    Intellisense / Autocomplete

    Those of you familiar with Visual Studio intellisense or more plainly “autocomplete” will like this feature. Enabled for Search boxes and New Contact screens, this hack dynamically suggests possible matches as you type in the field. This is useful for two reasons. Every now  and then I am looking for someone but for one reason or another I only know a part of their name. I don’t want to search, then look through the list to find it again – just once is enough! So I can do a partial match and after only 2 characters I am presented with up to 20 results that match the search pattern (anywhere in the word) meaning Da will match Dave Sobel and Tech Data.

    This also addresses uniformity during new account creation. Monkeys tend to just type crap in without looking whether the company exists or not – which is why CRM systems blow – nobody EVER pops up that window that gives you the company listing. In turn, they type in a slightly different company name and split the company intelligence, support, etc. This will hopefully stop that.

    Sm-preview2

    WhotheFareyou?

    Now contact details link for company and contact have been available since the first few months of Shockey Monkey – but in order to get some details you had to navigate to another page (or tab); sometimes just to check if the user is in your time zone or who the main contact for the account was.

    The contact and company fields can still be clicked on for full, editable, details – however – hovering over them will dump out a tool tip with the most interesting details (as determined by me)

    Sm-preview3

    Stupid Monkey Tricks

    Ok, this goes straight into the stupid area as far as I’m concerned but again, my monkeys seem to like it. You will notice the ticket update screen looks a little bit different.

    First – you can double click on the subject of the ticket, edit it inline and automatically save it on the backend without submitting a single form, refreshing a page, navigating elsewhere, etc. This was requested by Daryl and until today I just had no way of implementing this gracefully without 8 billion controls and junk. Now I do. I should just send Daryl a bill for this one.

    Second, the most common ticket update items are visible by default. The additional (now including priority updates as well as all else) stuff is stuck to the left of the ticket update which has been bumped up to 80 characters. People seemed to want more space. I guess I just leave really small ticket updates? Either way, its bigger now.

    Third, by default both billing and new private ticket screens are now hidden. Internal feature request: 80% of the time we are not entering billable time for service support unless it takes over an hour to do. So why should it be loaded and crowding things? That container is hidden by default but when you click on a little text that says “Click here to add time & billing information” it will slide the div into the view without a reload or refresh.

    Fourth, there is now a private / internal comment textarea. Why? Turns out we have a lot more to say on each ticket update than we want to share with the customer. We do more support internally than we do externally. Ticket update externally may say “Ok, please try this again and see if it works” while the internal ticket update reads “Believe this is triggered by bug #181, do we have an ETA when that shit will be fixed?” Same concept – slide in div, if you aren’t providing an update you don’t have to load a window. 

    Sm-preview4

    Thats just a little bit of eye candy to keep you guys thinking about tomorrow.

    Cool part? 90% of the above was directly influenced by the Shockey Monkey users suggesting and voting on features in the Features tab at support.ownwebnow.com; Amazing, ain’t it? Making money in the community without having to squeeze into a bike shirt 3 sizes too small.

    Parsing Email & Standards

    I’m by no means a newbie when it comes to parsing email but for the past few days I’ve been looking at the application contents of email messages and really wishing there was a standard, or perhaps a standard most people would adhere to.

    The big idea: Parse all incoming messages and handle support requests in one way, system alerts, notifications and application events in another.

    If you are using Shockey Monkey I really hope you can open up either a trouble or development ticket with a sample copy of the type of message you receive from the remote appliance, monitoring service, helpdesk, etc. The goal of course is to parse these dumb reports and apply some intelligence to them. For example, the alert you just got – is it just a notification you can’t do squat about (“Exchange is allocating more ram than usual”) or is it perhaps something you’d want to look at immediately (“Exchange mail store process has stopped.”); Thats just one of the examples but there are many different types of alerts and notifications that could be imported and managed in the system.

    I did get pretty creative with my parser security today. Checking if the user exists. If the user doesn’t exist, check if the message is coming from a host listed on a major RBL and if it is, don’t shoot back an automatic notification to help them sign up. If you just received a known notification don’t send back the reponse, just silently open one up in the Shockey Monkey portal. Copy X headers from the previous notification into the new one and simulate a reply instead of generating a whole new message. Track back and throttle senders. Control for possibility of infinite loops and temporarily graylist senders….

    You know, the fun stuff on a beautiful summer day 

    I’ve got to say, I am impressed with the way Shockey Monkey has been handling over the last few months. The load on the system has been growing exponentially but the resources seem to be very much in check. Wonder what happens when I introduce the AJAX patchset. I have to say that I love it on our portal but I’m also the one that designed it so…. huge grain of salt along with that one. 

    All caught up on Monkeys

    All the Shockey Monkey activations that were requested until today have been put into the provisioning process. So if you’ve ever applied for Shockey Monkey and never heard from me, it likely got eaten by your SPAM filter. Please reapply and whitelist ownwebnow.com domain in your app.

    There are only two reasons why someone would not get their application accepted:

    • Submitted an email from a freemail system
    • Web site or organization does not exist

    So if you sent me an email from aol.com, msn.com, gmail.com, yahoo.com, sbc.com or any other freemail system the message has been destroyed. System usually does this automatically, I wish I could reply to them all but there are so many form spam bots with those addresses that its impossible whats legit and whats fake. So use a business email address. Second reason for being denied would be the lack of a corporate web page. If I can’t tell that you have an online presence, I can’t extend the service to you due to some long standing legal concern. When/if that changes you’re welcome to reapply, I frankly don’t see these as big roadblocks to any established IT firm.

    So there is currently 0 backlog, everyone that wanted it (and met criteria above) is being taken care of – if you aren’t, hit the app again after you whitelist me.

    Thank you for your phenomenal, awesome and amazing support. 

     

    I want my Shockey Monkey!

    The pace of signups for Shockey Monkey is picking up for some reason. I don’t know why but I am guessing that the people using the monkey are really enjoying it and are recommending it to their peers - for that I thank you and I am very happy.

    I’ve taken a moment to write the following document that explains Shockey Monkey activation process. As you can tell, it’s quite simple.

    The big secret..

    I know what you’re thinking: “Big Bad Vlad the service automation programmer sure can’t automate things worth crap.” – So I’ll let you in on a little secret. Yes, this can be automated quite easilly. However, by making people jump through the hoops of updating their contact information, updating their corporate information, ordering a service, creating a new contact, updating and reviewing the support ticket and more I am effectively training the future administrators of Shockey Monkey on how to use the product. Yes, you can watch the video all you want and read the documentation but after you’ve been put through the paces you get the feeling for how the platform works, events and triggers, and by the time you’re in your portal you already know how it works, most importantly, you know how your clients are going to view this new thing you’re offering them.

    So you see, sometimes a lot of thinking goes into seemingly stupid decisions.

    Blazing the Monkey with AJAX: Caching AJAX javascript libraries for sites where data changes often

    Now that a lot of the logic behind Shockey Monkey has been solidified I decided it was time to optimize the interface performance a little bit. Truth is, there is a lot of minor updating that goes on behind the scenes that should not be calling for the entire page to be reloaded. Enter AJAX.

    I was talking with Pablo the other night about XHR and told him I was trying to use Script.aculo.us libraries but couldn’t really wrap my head around some of the stuff. So he showed me his blog which is tricked out with the Yahoo UI library (which I find ugly but to each his own) and explained to me how the whole thing works. Funny how its thing fall into place when someone explains it to you.

    So for the past day I have been Ajax crazy trying to nail down some of the effects and events. One of my cornerstone values for Shockey Monkey is that it be lightning fast. If I have to wait to get or input data I’ll open up Notepad (used to be Outlook before 2007 started getting non-response-happy all the time). And even though its a web app I have to say that I’ve really done a good job at keeping it very lightweight and fast.

    Speeding it up by slowing it down…

    So the AJAX premise is that you can speed up the interface by doing partial page rendering. The smoke and mirrors of it is that in order to enable all the cool effects, events and transitions you have to load up a very hefty Javascript file (mine comes out to about 268Kb).

    So yes, the partial screen rendering will be very fast because I am only loading some text into a <div> but what happens when they go from page to page? You’ve guessed it, JS reloads. Because the documents themselves change often I have a no-cache directive for the entire page meaning every time someone clicks on something that triggers the page reload the entire mountain of javascript gets pushed down. Click through four pages and you’ve pulled down over 1 Mb which would effectively make the entire web app crawl and put quite a sticker shock on the bandwidth bill at the end of the month.

    Guessing the right Google search string…

    There is no way that Google, Yahoo and all the other big league Web 2.0 players are constantly pushing down megs and megs of data during each session. Let’s face it, the events and effects code is in libraries which will rarely be changed so why make it take the pipe trip every time? After a  little bit of searching I found a way to do selective javascript caching from Ajaxian. The answer is actually in the comments but the question is outright scary:

    Our users have to download a 2MB ajax application every time they visit our website. It would be much faster if we could cache 90% of our application in the browser cache using this LRU Cache so that the next time the user visits our website, they only need to download a small 10K file!

    The answer comes further down from Vasili Sviridov:

        ### activate mod_expires
        ExpiresActive On
        ### Expire images and javascript 1 month from when they’re accessed
        ExpiresByType text/javascript “access plus 4 weeks”

    Dumping that into the .htaccess file to override default server config (hi Schrag) takes care of the problem completely. Just have to make sure you’re sending your Javascript as text/javascript and not part of your inline text/html page code and voila.

    Shockey Monkey Activationathon Tomorrow Night

    As is customary when I’m in town, Shockey Monkey activation night is tomorrow night. I plan to go through the last two weeks worth of backlogged orders and get as far as possible in four hours. If you’d like to hop to the front of that line, you’re in luck – just IM me at shockeymonkey@ownwebnow.com address via MSN Messenger.

    In order to qualify for this you must be signed up for Shockey Monkey already and you must meet the basic requirement of being a respected IT businesss (ie, have a web page and some sort of identifiable text as to what you do).

    The setup starts tomorrow night, 6/24/2007 at 8 PM EST.