130 likes | 526 Views
Feedback on the Bouygues Telecom experience with AppDynamics. by CYRIL VANLATHEM OSS FAI developer. 1 - Bouygues Telecom 2 - Why an APM on the OSS? 3 - Choosing the APM from AppDynamics 4 - AppDynamics at Bouygues Telecom 5 - Specific use case. agenda. 2. Key Figures. 3.
E N D
Feedback on the Bouygues Telecom experience with AppDynamics byCYRIL VANLATHEMOSS FAI developer C. VANLATHEM - PAUG June 2013
1 -Bouygues Telecom 2 - Why an APM on the OSS? 3 - Choosing the APM from AppDynamics 4 - AppDynamics at Bouygues Telecom 5 - Specific use case agenda C. VANLATHEM – PAUG JUNE 2013 2
Key Figures C. VANLATHEM - PAUG JUNE 2013 3
Key Figures Mobile Network Fixed Network • Extensive 2G/3G coverage, with higher forthcoming H+ speeds (especially 4G technology) • 99% of the population has 2G coverage, 96% 3G+ (up to 7.2 Mb/s), and 58% in H+, the fastest 3G speeds - up to 42 Mb/s • 15,000 relay antennas • Coverage in more than 250 international locations due to agreements with more than 530 foreign operators • Deployment of 4G began in 2012, with coverage in the city of Lyon • Over 10 billion euros invested in the network since 1995 • Bouygues Telecom is currently the only provider of ADSL, FTTLA (fiber optic with Coax Cable Termination), and FTTH (fiber to the home) • 4,800 connection nodes • 78% of households covered in unbundled zone • Almost 7 million households eligible for the very high fixed speed (THDF) due to an agreement with Numericable (2009) • 40,000 km of fiber • Access to THDF for over 13 million potential households due to agreements with SFR (2010) and Orange (2012) in both high and low density zones. C. VANLATHEM - PAUG JUNE 2013
Why an APM on the fixed OSS Supervision based on the thresholds IHM Sales/ IHM PNF / IHM Cdc / Diag / … Availability of front OSS Sale:Eligibility / OSS Guichet / NRMNAGIOS Requests Customer Reference BSS MAJ information feedback OSS Front OSS Front OSS Back OSS Back Référentiels techniques OSS Technical OSS standards PFS Network (SMV / DSLAM / ACS / IMS / Radius HS) MAJ MAJ Provisioning Provisioning Stream of orders Availability of the Provisioning chainsNAGIOS Operators/partners Relationship QOD: flows Consistency and OSS ref C. VANLATHEM - PAUG JUNE 2013 5
Tools Available In The APM (Application Performance Management) SpaceCriteria Used Following The POC. • Criteria for choosing an AMP: • Simple installation and configuration • Available for a variety of technologies (Java, .NET, PHP, etc.) • User-friendly interface for analytics • Cost • Support requirements taken into account • AppDynamics met all of these requirements: • Auto-discovery mechanism • Clear dashboard • Economical model based on the number of JVMs. C. VANLATHEM - PAUG JUNE 2013 6
AppDynamics at Bouygues Telecom Usage environment • Provisioning FAI • 40 JVMs Principal uses • Monitoring/Measuring=> Provide visibility • Supervision => Detect incidents more quickly • Diagnostic assistance => Reduce delays in incident resolution • KP assistance / Performance measurement => Anticipate problem points Forthcoming tasks to reach our target • Finalize JMX metrics • Create alerts • Interface with NAGIOS • Customize our dashboards • Preview monitoring of our new management system: Fulfillment Order Management Suite from TIBCO C. VANLATHEM - PAUG JUNE 2013 7
AppDynamics at Bouygues Telecom Immediate gains with respect to monitoring…. 8
AppDynamics at Bouygues Telecom …and with respect to error analysis 9
Concrete example finding the cause of a bottleneck of a (ST.)? • Symptom : Bottleneck in the ODYL domain • Functional impact: provisioning optimization process for stalls (?) • Technical mpact : frequent alarms being relayed to the cockpit (support level 1) requiring repeated stopping and restarting • Process: • Analyzing errors in the Errors dashboard => no significant problem found C. VANLATHEM - PAUG JUNE 2013 10
Concrete example finding the cause of a bottleneck of a (ST.)? • Nothing significant uncovered at the memory level when incidents occurred (Memory dashboard) • Nothing significant uncovered at the response time level when incidents occurred (Slow Response Times dashboard)
Concrete example finding the cause of a bottleneck of a (ST.)? • Observation of different indicators and metrics available from AppDynamics:: • Detection of regular saturation of a connection pool (?) • Discovery of an anomaly • Correction of the anomaly • Re-establishment of service confirmed by various measurements Connection pool utilization on the ST (?) C. VANLATHEM - PAUG JUNE 2013