This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Sync’d Compartmentalized Common Operational Picture: SC2OP
1
SAW Concepts LLC Modified Presentation to NYC Computer
Feedback Monitoring – Working with Business Units to Determine Business Application SLA Criteria
Topics:1.Dangerous assumptions planning THRESHOLDS for new business applications2.Best practices for planning threshold management for new business applications
Feedback Monitoring:-Heartbeat msg update: y/n-Update = new netconfig
planning thresholds for new business applications> / < threshold by intensity, duration, magnitude… threshold rules dictate alert and event feedback to mitigate / adjust & reform orgs..
New business partner is actually subsidiary and previously booked through airline, but not by leveraging their real-time systems.
Business unit announces new partnership, but not details of new business application.
Business unit understands that middleware group has handled this type of data transaction before.*
Business unit and middleware group do not meet to review new application criteria, only details of middleware objects needed.
Business unit assumes similar thresholds will monitor this application the same way; “this one’s not too different!”
DoD systems: driven by Structured military message Threads that along with theIndividual FFURNS and FFUDS[data elements as 3 / 4 digit codes] Determine funding and developmentSchedule and pace – often, single data elements take over a year to NOT change – e.g., the infamous redThread where an AVIATION data element was the fly in the ointment between a ground system and a intelligence system – true story!
Multiple Queue Managers with multiple Queues associated with “each” different business application.
Different business applications exist on the same Queue Managers - in order to leverage server capabilities.
Different applications built by different business units, different development staff, different business requirements, different system footprint - all on same server!
Administrators assume similar thresholds will monitor all of the different applications the same way; “this one’s not too different!”
The Heart Beacon involves pre and post configuration management of the network and is neutral to systems and middleware. What Vinton Cerf and his team described metaphorically as the heartbeat is actually a interval in time where (state meta) data is gathered and placed into temporary holding areas, queues, file structures for onward delivery by middleware software such as agents, bots, motes, scripts. The heartbeat is an opportunity in time to synchronize data harvesting protecting bandwidth on low capacity networks prior to entry into portals and fusion centers – the point of no return in context with event time stamping. After transition to the middleware or cloud layer, it is too late to try and re-establish timing of event / alert chain of custody. Many systems report the same event at different time intervals. Too fast updates tend to saturate the network. Too slow refresh rates cause the data to be too “stale” for targeting systems. Operational discipline derived from years of military testing and simulation is reused across the entire portfolio of assets / applications.
The Heartbeacon is neutral to middleware – HOWEVER! Not all Middleware is created with the same design / functionality. The Heart Beacon involves gathering state meta data via the heartbeat andPlacing this data (state meta data snapshots) into temporary QUEUES And other temporary structures for onward delivery to the System Administrations (S-6’s) who concatenate this data into heartbeat messages. A change in the platform / user state must be monitored andUpdated and is THRESHOLD sensitive – a user / platform that hasn’t responded is said to be “stale” and shown in the application accordingly
Queues // Thresholds
6
Fares
Crew
Departure
Cargo Reservations
Ticketing
CodeShare
Mechanics
Qmgr - AAA
Qmgr - BBB
Qmgr - CCC
Qmgr - DDD
Only one problem:
This is only 1
server in 1 airport!
Example Application EnvironmentHeart Beacon option: The TCP/IP sub-protocol’s heartbeat function acts as a mini publish-subscribe mechanism that is set to gather state meta data from cloud-subscriber-user at pre-defined intervals by cloud-subscriber-administrator. State meta data is temporarily transferred to files, QUEUES, folders, caches and other temporary data storages awaiting pick up by transport-agent to the cloud-management-broker that aggregates cloud-subscriber-user state management data into heartbeat state management snapshots (REST Representational State Transfer compliant) for onward replication (copy) to other cloud-subscriber-administrators to effect inter and intra cloud infrastructure changes accommodating group adhoc spontaneous integration and cloud-subscriber-GROUP (described by Organization Identification ORG ID) affiliation / de-affiliation based on current mission, operation, scenario goal.
QUEUE MANAGER = Perfect for the Heart Beacon
7
Qmgr - AAA
Qmgr - BBB
Let’s Multiply!
Fares
Ticketing
Fares
Ticketing
Fares
Ticketing
Fares
Ticketing
Fares
Ticketing
Qmgr - BBB
Qmgr - DDD
Crew
Mechanics
Crew
Mechanics
Crew
Mechanics
Crew
Mechanics
Qmgr - DDD
Fare Quotes are being processed by all endpoints.
Typically Overlooked:
Are there other apps [Blue
Force Tracker] running on those
endpoints?
Departure
Cargo
Departure
Cargo
Departure
Cargo
Departure
Cargo
Qmgr - AAA
Example Application Environment
Net Centric Warfare Challenge – propagate Sync delta message to update Concept of operations across many networks / subnetsThat are in flux – constantly monitoring end points / platforms / sensors / soldiers
More than 1 type of Blue Force Tracker! Land Warrior/ Grenadier Brat.. Apps for different business units
Which endpoints more closely match the PROFILE of travel portal customers or
GEOGRAPHY of portal
customers ?
Departure
Cargo
Departure
Cargo
Departure
Cargo
CodeShare
Reservations
Qmgr - AAA
Example Application Environment
User Profile: Role By OrganizationalType – ORG IDOr type of device:URN: Uniform Resource Name
Each Heartbeat Interval, the geo-location or 10 digitGrid coordinate isSampled. Change in geo-loc isExtrapolated into State – moving, halt, stale, in-op..
9
Fares
Qmgr -EWR
The MQ Admins get ready for a long night because alerts will be firing often based on old traffic patterns. The Biz units get calls wondering why customers are calling in because of slow response times for quotes. Are the servers tuned and optimized? Yes – that is not the issue.
Qmgr - CCC
TravelPortal
Qmgr - DDD
AirlinePortal
Fares
Qmgr - HPN
Fares
Qmgr - LGAEach Unit has its own assumptions of typical business transactions.
Example Application Environment
Beacon Tech / Avada = millisecond response
Disciplined process & temporal sampling discipline protects bandwidth And limited physical resources e.g., server cycles & available time slots Traffic patterns change = network changes
The MQ Admin has scope to all Qmgrs, Queues, etc. & partial authority to change attributes and settings.
Infrared360 enables role-based visibility into application environments
ROLEBASED
FCC Command &
Control Management
Framework
Heartbeat message#73334 accept / delay
ORG ID / URN
“Rose Colored” Glasses
11
Collaborative, Delegated Management
LGA Qmgrs
Win2kOS/390 AIX
AS400
HPUX
Linux
http http
HPN QmgrsEWR Qmgrs
Solaris
JFK Qmgrs ISP-Qmgrs
HP-nonStop“Invent”
Fares app team = “TF Bling-Bling”
MQ Adminteam
The Fares Biz Unit has scope to only the Fare application Objects, but no authority to modify them.
Infrared 360 enables role-based visibility into application environments
Get / put state meta data from cloud-subscriber-user at pre-defined intervals by cloud-subscriber-administrator. State meta data is temporarily transferred to files, queues, folders, caches awaiting pick up by transport-agent to the cloud-management-broker that aggregates cloud-subscriber-user state management data into heartbeat state management snapshots (REST Representational State Transfer compliant) for onward replication (copy) to other cloud-subscriber-administrators to effect inter and intra cloud infrastructure changes accommodating group adhoc spontaneous integration and cloud-subscriber-GROUP (described by Organization Identification ORG ID) affiliation / de-affiliation based on current mission, operation, scenario goal.
Access to target objects are secured by group and role permissions and audit trails mark every action taken
“The GRAIL”
SC2OPHeartbeat Sync Delta message
# N, N +1 accept / delay
12
Collaborative, Delegated Management
Travel-Portal
LGA Qmgrs JFK Qmgrs
Win2k
OS/390 AIX
AS400
HPUX
Linux
http http
Solaris
HP-nonStop
Fares app team
Travel Portal team
MQ Adminteam
The Travel Portal Biz Unit has scope to only the interface to airline fare quote system.Infrared360 enables role-based visibility into application environments
An Interactive ApproachHow do these biz units collaborate to adjust monitoring thresholds for the new Fares application and associated promo?• Feedback Monitoring: “A practical approach to working with Business Units”
Modelling New Business Applications • Review expectations and tactics with business units.• Gather statistics over short intervals during initial rollout.• Determine and set threshold values to watch – initial hours.• Gather statistics over medium intervals during initial rollout.• Determine and set threshold values for comfortable limits for
that day (8am-11am, 11am-2pm, 2pm-5pm, 5pm-8pm).• Gather statistics over longer intervals during initial rollout.• Determine and set thresholds values based upon daily totals, then based upon each daily pattern for that week.• Monitor thresholds for THIS APP should now be in place.
• Use same feedback loop in early production monitoring for each unique application !!!
• Collaborative visibility to business applications environments• Short, mid, long term threshold alerting• Real-time middleware object detail statistics visibility• Comparative statistical charting of real-time middleware objects• Real-time administrative interface to problem area for quick problem resolution • Self-healing capabilities ties alerts to pushed Admin changes• Automated replay and volume testing of real transactions• Instant visibility to application environment without pre-set monitoring infrastructure