Skip to main content
CRM messes - Ticketing systems

I was meeting with the guy that is in charge of the CRM stuff here. He does most of the support, upgrades, and projects around them all. We use some big ugly CRM system (leaving out the name, because I don't like them at all). I have asked his boss a couple times about moving to It would save us a lot of money and time. Its taken 2 years, but they finally listened and are making the plunge. Its good to see that they are finally evolving off the crap they currently support, upgrade and deploy. The project is estimated to take 5 years. They are also moving parts of it (accounting) onto SAP, which is a great move too.

We have a lot of different ticketing systems too. We are trying to consolidate them into one set, but people seem to be moving in different directions. I deal with 5 systems currently. Each of them are pretty poor and overly complex IMHO. Some have bad workflow, some have bad reporting, and none seem to integrate with email.

If i spend most of my time in email or on the web, why can't I integrate those systems into my existing workflow (browser extension, or email based workflows). They all just generate an email and you have to login to see what's happening.

I prefer something nice with email integration like Cerebrus Helpdesk -

Its cheap too!


Popular posts from this blog

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later.
Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not?
Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting with an API, t…

F5 Persistence and my 6 week battle with support

We've been having issues with persistence on our F5's since we launched our new product. We have tried many different ways of trying to get our clients to stick on a server. Of course the first step was using a standard cookie persistence which the F5 was injecting. All of our products which use SSL is being terminated on the F5, which makes cookie work fine even for SSL traffic. After we started seeing clients going to many servers, we figured it would be safe to use a JSESSIONID cookie which is a standard Java application server cookie that is always unique per session. We implemented the following Irule (slightly modified in order to get more logging): (registration is free)
# Check if there is a JSESSIONID cookie
if {[HTTP::cookie "JSESSIONID"] ne ""}{
# Persist off of the cookie value with a timeout of 2 hours (7200 seconds)

NPM is Broken

As someone who bought and implemented NPM solutions, covered them as an analyst, and now watches the industry, one cannot help but notice that NPM(D) is broken. According to Gartner themselves, the data center is rapidly changing, the data center is going away, maybe not as quickly as Capp states, but it’s happening. This is apparent by the massive public cloud growth posted by Amazon, Microsoft, and Google in their infrastructure businesses. This means that traditional appliance-based NPMD offerings will not work, nor will traditional ways of collecting packet data. Many of the flow offerings do not handle the new types of flows which these services generate, but most importantly they do not understand the internet, which is the most important part of assuring services in cloud hosted environments.
The network itself is not just moving to overlay a-la NSX and ACI, it's moving inside of orchestrated containers, and new proxy/load balancing systems typically built off components or …