Skip to main content

Business Intelligence for Infrastructure Monitoring

How cool would it be if you could look at your servers behind a VIP on a load-balancer and tell which servers were serving more errors, serving traffic slower, or not getting the requests they should be in comparisons to your other servers. I have a product in place to do just this, its not released so I can't talk too much about it.

The issue is that we have to embed some of the data in the http requests, or cookies, which I need help from development to do. I am getting pushback about security, and information disclosure which I am fighting through. I understand it could be an issue, but it's the only way that we can properly track usage and performance. This would rally help a lot to have as a internet based standard for tracking requests and backend connections and usage. Using weblogs is not feasible when you have thousands of servers that don't have any consistency. This is my first pass at what I want to add to the http headers:

Type

Variable Name

Explination

Sample code

Application

ApplicationName

StockTickerApp

 

Application

ServiceName

TickerWebService

 

Application

PageName

Login_Page

 

Application

TransactionID

Unique ID of request

 

Infrastructure

ServerID

Something like fcweb01 + last 3 from ip range (.124) fcweb01124

 

User

UserName

Bsmith

 

User

CompanyName

Customer ABC

 


 

More on this later.

Comments

Popular posts from this blog

Dynatrace Growth Misinformation

For my valued readers: I wanted to point out some issues I’ve recently seen in the public domain. As a Gartner analyst, I heard many claims about 200% growth, and all kind of data points which have little basis in fact. When those vendors are asked what actual numbers they are basing those growth claims on, often the questions are dodged. Dynatrace, recently used the Gartner name and brand in a press release. In Its First Year as an Independent Company, Gartner Ranks Dynatrace #1 in APM Market http://www.prweb.com/releases/2015/06/prweb12773790.htm I want to clarify the issues in their statements based on the actual Gartner facts published by Gartner in its Market Share data: Dynatrace says in their press release: “expand globally with more than three times the revenue of other new generation APM vendors” First, let’s look at how new the various technologies are: Dynatrace Data Center RUM (DCRUM) is based on the Adlex technology acquired in 2005, but was cr...

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...

IBM Pulse 2008 - Review

I spent Monday-Wednesday at IBM Pulse in Orlando. It was a good show, but quite a few of the sessions were full when I arrived. It was frustrating because they didn't offer them more than once. The morning sessions were mostly pie in the sky, and not very useful to me. I got to spend a lot of time with senior people in engineering, architecture, and acquisitions/strategy. I also got to meet people I knew from online or other dealings with IBM. Overall, the show was a good use of my time, and I found it enjoyable. Here are some of my highlights: ITM 6.2.1 improvements including agentless capabilities and such. New reporting framework based on BIRT which will be rolling forward. New UI which is being pushed and was on display from TBSM 4.2. Hearing about what other customers are up to (mostly bad decisions from what I've seen). Affirmation of ITNM (Precision) as a best of breed tool, with a excellent roadmap. Some things which are bad and make no sense: Focus on manufactur...