Hariram Hari – Enterprise IT expectations on Monitoring solution

1. www.icinga.org www.fortidm.com
ENTERPRISE IT EXPECTATIONS ON
MONITORING SOLUTION
Fortidm Technologies - Partner of ICINGA

2. Fortidm Technologies – Founded in 2005
• Cyber Security, Audit and Advisory Services
• Enterprise & Cloud – IT Infrastructure architecture, design,
implementation and migration
• Open Source App Dev/DevOps– Mobile, Web application
development
Who we are

3. FORTIDM is
• Ranked Top 10 Vulnerability Management Solution
Provider - 2017 by ESM
• Rated "exceptional" with top 7 % in the SMB IT service
sector by Dun & Bradstreet
Credentials

4.  How to choose a monitoring solution that fits all aspects of a large enterprise that
typically has multiple heterogeneous platforms, protocols, applications, services such
as VOIP Telephony, mainframe, storage, all kinds of complex systems?
 There are proprietary tools from CA, HP, BMC, EMC, IBM, Microsoft etc. for
enterprise monitoring. However, organizations – large, medium or small often realize
that they are spending huge amounts but the solutions do not cater to all the needs
causing spawning of multiple tools in their Enterprise
• Proprietary tools (compared to standards based) is a source of Integration
complexities
• License limitations and spiraling cost on scaling
• Tools control the business process (as opposed to business process using right
tools) causing process inefficiency
• Dependency on vendor for custom requirements
• Vendor Lock-in
The Challenge

5. • Architecture blueprint needs to cover
• Standardized Framework (ex: Reference
Implementation)
• Process and governance
• Holistic approach to enterprise monitoring
Standardized approach to Monitoring

6. LET US GET STARTED…

7. Complex Process-Technology mix
• Mainframe
• Networking
• Databus or integration platforms
• Open systems (servers, platforms and storage)-Physical/virtual/Cloud
• VOIP and SIPS Telephony
• Help Desk integration with ServiceNow, Remedy etc.
• Applications (web, mobile)- HR, Finance and business applications
• Database
• Social media integration
Typical large scale enterprise consists of

8. • Consolidation of tools for monitoring
• Integration needs as the business changes
• Agility to adapt to newer capabilities
• Continuous integration and automation
• Elimination of unnecessary tools
• Cost control
• Improved QoS
Next Generation Monitoring

9. • Standardized framework with all hooks for enterprise
components helps in communicating the architecture
holistically
• Abstracts of cookie cutter implementation for enterprise
gives a warm and fuzzy feeling of ICINGA as a product
for enterprise monitoring
• Demo platform that showcases the above framework
built and ready to use for client demos
Need for ICINGA Eco-system framework

10. • Agents for monitoring specific mainframe
sub-systems (e.g. CICS, DB2, IDMS, M204,
ADABAS,VTAM/TCPIP)
• z/OS & z/VM, z/LX – Are Agents available?
Typical Requirements- Mainframe

11. Typical Requirements- Database
To replace ADHOC Database Tools for monitoring
and capacity planning including, but not limited to:
regression analysis, alerts for tablespace
thresholds, filesystem space thresholds, expiration
of digital certificates, wallet status(open/closed).

12. Typical Requirements- Database
Assessment of database/SQL code performance ,
space utilization, memory utilization etc. and
calculate optimal recommendations to modify
database environments and create Incident Tickets
with these recommendations.
These Tickets to be reviewed by DBA group and
sent to Application Teams to make modifications, as
necessary.

13. • Coding Languages for which deep code inspection
agents to monitor byte code processing
• Trace transactions when SSL is employed between
application endpoints with different security
certificates?
• Capability to provide a profile of the execution of
each thread within an application?
Typical Requirements- Application

14. Typical Requirements
Active Discovery
Build application map using Active Discovery,
Transaction information and network packet
capturing
Storage
• Windows Folder Synchronization/Migration
• Windows Fileshare Auditing (file/folder
auditing for modify & deletes)

15. Typical Requirements- App/Transaction
Trace transactions that convert from one
type/protocol to another (e.g. HTTP -> MQ
Message -> XML -> JDBC)
Monitor user's transaction through a proxy or
cloud (Limelight/Akamai)?
Deep inspection agents for Application Servers
Canned reports for application scalability

16. • Effective communication to appeal enterprise scale
monitoring expectation
• Need for improved marketing collaterals for partners
• Holistic approach to transition the enterprise to the
next generation solution by consolidation, integration
and process centric approach
Summary

17. Q&A

18. Thank You!