Skip to main content
I live in Boston, but I have to go to New York a lot for work. The joys of day trips. So I had meetings this morning from 8:30am until now... around 2pm. I have been talking to a lot of people about some of the work I am proposing we do around here:

1. Fix entitlement systems - replacing them with off the shelf software (SSO and IM).
2. Figure out application dependencies - by using tools like nlayers
3. Build a SOA management infrastructure - by using tools like Actional and Amberpoint

Figure out how we are going to build a CMDB with the data we get from these tools. What vendors are good for CMDBs.

Any advice on CMDBs?

Can any of the SOA tools build the dependency maps? From what I understand and have been told by vendors they will build some of these maps. At least logical layer maps, that's a good first step.

I need to figure out how to feed this data to our business folks and give them usage, cost, and consumption numbers. If we can do that then we will really be making progress on this stuff.

This goes into monitoring and moving from active monitoring to passive and real-time monitoring. Understanding behaviors and anomalies or stastical deviation as an alarm. Move from building manual monitors into actually monitoring the behavior of a lot of metrics and then alerting based on changes of those. These are forward thinking ideas that we need to bring us into a proactive and predictive mode from a reactive mode.

How about product usage analytics capability and usage tracking. That's another project I am working on. Many proposals on the table here.


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 wi

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, m aybe 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 component

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) when HTTP_REQUEST { # 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) p