New Relic - Demotron Treasure Hunt

Last updated: Sept 15th, 2019
Treasure Hunt Progress:

The New Relic Treasure Hunt!

Ahoy there! The New Relic Treasure Hunt is a fun way of experiencing the New Relic platform - in the context of a demo environment where some known issues are happening. As a practitioner in the world of modern Digital development and operation, you will face many of these challenges in your own world. The Treasure Hunt will guide you through several scenarios where observability and insight may lead you to better outcomes. Happy hunting!

1. The Bug Hunt

After a long voyage at sea - you’re settling down for a tot of rum and hard-tack, only to be interrupted by a text indicating your critical pirate WebPortal is having an issue. What do you do next? For most folks without an APM solution, the story is archaic: log into machines, sift through large log files, and inevitably guess at what is occurring. New Relic makes this story a non-issue by allowing you to quickly hone in on the specific cause of any issue quickly and within context.

Partner Demotron Link

Treasure Hunt Challenges

  1. Which transaction is suffering?
  2. Looking within a transaction trace - can you identify which segment is causing the issue?
  3. What caused the issue?
  4. Bonus Mark - who caused the issue?
  5. How did the issue get resolved?

2. Special Delivery

After getting marooned on a desert island for days - and running out of supplies - your pirate friends place an emergency online delivery on your platform for a new barbeque. The trouble really starts when they start fighting each other because the online shopping experience is terrible on their pillaged smartphones. What’s going wrong with the user experience in the WebPortal?

Partner Demotron Link

Treasure Hunt Challenges

  1. What's the most common cause of error?
  2. Over the last month, what part of the world has suffered the worst performance?
  3. Which of the following alert conditions are configured for browser metrics?
    High WebPortal CPU
    Slow Browsing on WebPortal
    Abnormal traffic spike
    High WebPortal Response Time
    High WebPortal DOM Processing Time
    External Service Failure
    Low volume of Ads being served
    High introduced error rate

3. Getting ahead of the curve

A good pirate is always planning ahead - and how better to do that than with Synthetics checks? A synthetic check is emulating real user activity on your webpage or API - and reporting the results. In this treasure hunt - we want you to find the slowest of the APIs - and then to use Insights to create a dashboard showing where the API performance can be improved. Partner Demotron Link

Treasure Hunt Challenges

  1. In Synthetics - find the page with the slowest API invocations and highlight where the performance problem is. Paste the URL below:
  2. Head to Insights. Query the SyntheticRequest namespace. What’s the 95th percentile of duration for the http://coretron.telco.nrdemo-partner.com:80/ API in the last month (closest answer please)?
  3. Using the FACET keyword - what is the URL with the highest average duration?

4. Tying Everything Together

Understanding metrics and events is important - but when you’re planning any sort of refactoring or re-architecting to more ephemeral architectures - understanding the dependencies and relationships is even more fundamental. Fortunately - New Relic One takes a fresh view. As the industry’s first entity-centric observability platform - we can easily find a way of navigating through the relationships - whether infrastructure, application, external service - or anything else.

Partner Demotron Link

Treasure Hunt Challenges

  1. Looking at the Inventory Service. How many hosts does this service depend on?
  2. What type of database is being used?
  3. What tables are being used by the service?
    plan_select
    inventory_table
    phone_table
    phones_table
    uid_table
    demotron_table
    plan_instance

5. New Relic Logs

Everyone knows that Pirates have a horrendous reputation for maintaining their own logs. But why should they bother - when they can leverage New Relic Logs to dive into deep contextual information from a wide range of log sources? Navigate into New Relic logs from the NR1 homepage and answer the following:

Partner Demotron Link

Treasure Hunt Challenges

  1. Looking at the Tower-Portland service, which of these actions is NOT present?
  2. How often does the 'systemd: Created slice User Slice of root' entry occur?
  3. What is the origin of the systemd log entries?