DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Troubleshooting App Performance Problems Using Instana Application Perspectives

Let's look at an example troubleshooting workflow using Application Perspectives to see how easy it is to find root cause.

Jim Hirschauer user avatar by
Jim Hirschauer
·
Aug. 26, 18 · Tutorial
Like (3)
Save
Tweet
Share
3.64K Views

Join the DZone community and get the full member experience.

Join For Free

one of the greatest benefits of the new application perspectives user experience is the ability to quickly identify and troubleshoot problematic services and requests.

instana’s new application perspectives capabilities provide a level of personalization that, up until now, has never been available in an apm tool. the ability to customize the definition of an application at any time, with any services, using any tag or label, provides the ultimate flexibility to monitor your applications in the way that makes the most sense to you. in this post, we’ll explore an example troubleshooting workflow to see how easy it is to find the root cause of poor performance.

stan’s got your back — automatic root cause analysis

a core tenet of instana has always been to automatically detect performance issues and provide automatic root cause analysis. we accomplish this using a combination of 3 key capabilities:

  1. automatic anomaly detection based on machine learning
  2. expert knowledge that detects problematic patterns
  3. dependency and event correlation to differentiate cause from effect

this results in the creation of an incident within instana and an alert sent to your operations center.

instana-incident-automatic-root-cause

notice in the incident shown above that instana differentiates between the “triggering event” (the reason the alert was fired) and the other events that are directly correlated and provide information on the root cause. in this case, the shop service ran out of memory due to our restrictive configuration.

this functionality is excellent for quickly identifying and resolving incidents, but what if for some reason a problem occurs that is not automatically identified? can you easily find issues using the instana ui?

looking for trouble — finding performance problems on your own

the answer is yes , it’s easy to use instana’s new application perspectives capabilities to find performance problems on your own. every new application perspectives screen provides charts and tables that bring the worst performers to the top. let’s look at an example…

poor-application-performance-troubleshooting-workflow-loop

the animation above shows the following sequence:

  1. choose your application perspective to analyze
  2. select a poor performing service from the “top services” table
    top-service-latency-list
  3. select a poor performing endpoint from the “top endpoints” table
    top-endpoints-latency-list
  4. select “analyze” to see all the poor performing traces in that endpoint
    transaction-trace-analytics-list
  5. analyze the slow traces to see why they are slow
    slow-transaction-trace-details

in this case, you can see that our payment transactions are waiting on an external payment provider (note: we artificially induced slowness into the external service call to paypal for this example).

slow-external-service-call-details

personalized apm or every situation

it’s easy to use instana’s application perspectives to troubleshoot performance issues. the combination of a personalized apm experience, curated dashboards, and automatic root cause analysis mean that you’ll be able to quickly identify and resolve issues in any situation. request your free trial of instana today.

application app

Published at DZone with permission of Jim Hirschauer, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • The Changing Face of ETL
  • Connecting Your Devs' Work to the Business
  • Learning by Doing: An HTTP API With Rust
  • Silver Bullet or False Panacea? 3 Questions for Data Contracts

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: