Scribd
Upload
51 views2 pages

Trouble Shooting Process

The document discusses five common issues that can hamper cloud performance: 1) Reliance on public internet which can limit performance due to traffic and throughput impediments, 2) Experiencing high application latency when infrastructure is housed in isolated private data centers far from interconnecting services, 3) Lack of integration between applications when some applications are held locally while others are on cloud servers, 4) Having an internal skills gap to manage critical tasks like performance, network security, and storage due to complexity of enterprise requirements, 5) Performance being hampered by legacy applications that are better suited to run on-premise rather than public cloud. The document provides tips for troubleshooting issues by defining the problem, finding the root cause, developing

Uploaded by

gogula sivannarayana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
51 views2 pages

Trouble Shooting Process

The document discusses five common issues that can hamper cloud performance: 1) Reliance on public internet which can limit performance due to traffic and throughput impediments, 2) Experiencing high application latency when infrastructure is housed in isolated private data centers far from interconnecting services, 3) Lack of integration between applications when some applications are held locally while others are on cloud servers, 4) Having an internal skills gap to manage critical tasks like performance, network security, and storage due to complexity of enterprise requirements, 5) Performance being hampered by legacy applications that are better suited to run on-premise rather than public cloud. The document provides tips for troubleshooting issues by defining the problem, finding the root cause, developing

Uploaded by

gogula sivannarayana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Troubleshooting cloud performance – Five common issues

1. Reliance(dependence on) on public Internet


- Engaging with scores of customers, regardless of temporal or
geographical boundaries.
- Using public Internet as a cloud gateway can mean that performance is
limited by traffic and throughput impediments

2. Experiencing high application latency


- Housing your cloud infrastructure in an isolated private data centre
commonly results in low-density connectivity and latency issues caused by the
distance between data centres and interconnecting services.
- These latency issues slow down internal operations, and ultimately
impact customer outcomes.

3. Lack of integration between applications


- Applications are able to 'talk to each other' are linked at the back
end via APIs
- Some applications being held locally while others live on cloud
servers
- Gartner predicts that through 2018, 90 per cent of organisations will
lack an application integration strategy, resulting in integration disorder,
greater complexity and cost.

4. An internal skills gap


- One of the most common issues in building and maintaining a cloud
environment is complexity.
- Complex the enterprise requirements, the greater the need for
specialist skills to cut through this complexity.
- Hindered by the lack of internal cloud expertise to manage critical
tasks such as performance, network, security and storage

5. Performance being hampered by legacy applications


- In building a cloud environment, it is commonly found that not all
applications are suitable for the cloud.
- Some legacy(money earning) applications are better suited to run on-
premise rather than in a public cloud environment.

TRICK:
When you encounter a problem, investigate it by eliminating as many unknowns
as possible. Try to get the simplest possible example of what you want to achieve
working first.

DEFINE THE PROBLEM


Data collection by "Questions asked"
Q1: What is occurring ?
Q2: When did it start ?
Q3: Who is being affected ?
FIND THE ROOT CAUSE

DEVELOP A ACTION PLAN

PREVENTIVE MEASURES

SOLUTION DOCUMENTATION
- Record detailed records
1. What was the problem ?
2. Who was affected ?
3. How were they affected ?
4. What steps were taken ?
5. Potential solutions considered ? Why ?

HOW is the questions - Lets start the list.

1) Can log into the dashboard - I have tested


2) Events received by the producers(HTTP, TCP, NICE, BROADSOFT, WEBSOCKET) - Can
the team check this now?
3) Check Processor and see the events received in the producers are hitting the
processors. Roughly http-producer contributes to 80% of the events by processor.
4) Check Firebase. - define metrics to look to make the determination
5) Check Mongodb - define metrics to look to make the determination
6) Check Redis - define metrics to look to make the determination

These are temporary way to determine impact until we establish a synthetic


monitoring.

You might also like