Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

A method to enable high level performance collection & analysis utilizing light weight MetaMessages

IP.com Disclosure Number: IPCOM000237625D
Publication Date: 2014-Jun-27
Document File: 7 page(s) / 192K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method to enable high level performance collection and analysis utilizing light weight meta-messages is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 01 of 7

A method to enable high level performance collection & analysis utilizing light weight MetaMessages

Disclosed is a method to enable high level performance collection and analysis utilizing light weight meta-messages for distributed systems. The disclosed method can measure the multi-system nature of distributed systems as well as optimizing measuring/monitoring for those distributed environments.

Current performance methodology:

Recording performance measurements typically occur at the server level because the complete software product was installed and operated within a single instance of an operating system (OS). The servers include authorization and authentication (ie: Lightweight Directory Access Protocol (LDAP)) and network (ie: Domain Name Server ( DNS)) and database storage. Even in a clustered environment, each server is measured separately. Examples of metrics used include,for example, CPU activity, network activity, disk activity, and memory usage.

To facilitate composite systems analysis, a common unit of computational / messaging work called the Meta-Message is defined. This metric can be computed from existing performance analysis sources and/or proxy plug-ins installed on each system in the environment.

Some definitions:


System: The sum of all nodes that comprises the server product, i.e.: Server product cluster, DNS server(s), Network File System (NFS) server(s), authentication server(s), edge server(s), Hypertext Transfer Protocol (HTTP) server(s), etc.

Node: An individual computing object that sends and/or receives some sort of message(s) to and from other nodes in a system and performing a unit of work. This

includes a running server application of any type. This may be an individual JVM


*

instance; one of the many separate processes in a server product that sends/receives messages, etc. These nodes need not reside in separate OS instances: for example, more than one JVM can exist in a single OS instance and those JVMs can be sending and receiving messages.

Message: A digital object containing information or commands or heartbeat or anything else that travels between two or more nodes in the server product farm (the system). The path used by the message(s) can be network, named pipes, shared memory segments, etc.

Meta-Message: The metadata messages generated by this solution.

Complex enterprise level software offerings by their very nature send messages between the server components (nodes). Think: message queue (ie: ActiveMQ* or WebsphereMQ*); Java JMX; network packets; DNS requests; document payloads; database queries, etc. These all can be generalized into a common concept called a Meta-Message that has definable attributes shown in Figure 1.

All messages have a single "source".


A.

1


Page 02 of 7


B.

A message has a "size" (ie: size in bytes)

All messages have one or more...