Observability
300-level live demo
| DEMO OVERVIEW | |
|---|---|
| Scenario overview | This demo shows how IBM Instana helps quickly identify and resolve an incident in a microservices-based application. The application in this demo is called Stan’s Robot Shop, and it uses various technologies such as Java, Python, and MySQL. |
| Demo products | Instana |
| Demo capabilities | Dependency mapping; Intelligent alerting; Distributed tracing |
| Sales guidance | Download the sales guidance document here. |
| Demo intro slides | Download the Introduction and Overview slides here. This is a short deck of customer-facing slides that sets the context for the demo. |
| Demo script | A complete demo script is on the second tab above. You can download a printer-ready PDF of the demo script here. This demo script has multiple tasks, that each have multiple steps. In each step, you have the details about what you need to do (Actions), what you can say while delivering this demo step (Narration), and what diagrams and screenshots you will see. This demo script is a suggestion, and you are welcome to customize based on your sales opportunity. Most importantly, practice this demo in advance. If the demo seems easy for you to execute, the customer will focus on the content. If it seems difficult for you to execute, the customer will focus on your delivery. |
| Demo guidance | The demo environment is set to automatically inject an error into the application once every hour. The cycle begins on the half-hour (so 9:30, 10:30, etc). You should see errors begin to show up a few minutes after this (around 32 or 33 minutes past the hour). The error will resolve itself and go back to a normal state after about 10 minutes. There are two options for how to give demos, given how this demo environment functions: 1. Schedule a meeting so that you can begin a live demo at 30 minutes past the hour. This will allow you to show the active incident in real time. 2. Run through the demo flow using a past incident. You can set the time period to when an incident was active (instructions are in the demo script). You will be able to run through the same scenario, except it will not show the incident alerts on the events icon on the sidebar. |
| Customer-ready demo video | View the demo video here. This is a short, but detailed, hands-on walkthrough of the scenario. The video is customer-ready. Potential uses of this video are: 1. Familiarize yourself with the details of this scenario 2. Gain customer agreement that they would like to have a tech-seller do a deep-dive demo of this scenario 3. Use as a prospecting tool to generate customer interest in these capabilities |
| Customer-facing expert guidance | Observability is the new APM for cloud-native applications. |
| Required versions | Instana 3.213 |
| How to get support | • Open a support case at IBM Technology Zone Help regarding issues with reserving and provisioning Tech Zone environments. • Contact #platinumdemos-automation-support regarding issues with setting up and running this demo. |
PREPARE TO GIVE THE DEMO
1 - Environment setup (live incident)
If you will demonstrate using a live incident (i.e. beginning the demo at 30 minutes past the hour), follow these steps.
No additional setup is needed.
1 - Environment setup (past incident)
If you will demonstrate using a past incident, follow these steps.
Since you will be demonstrating using a past incident, you will need to set the time period.
1. In the upper right, click the button showing the timeframe.
- At the bottom of the pop-up, set the timeframe to begin at 25 minutes past the hour and end at 35 minutes past the hour. It doesn’t matter which hour you pick. Click Set Time.
- Check that the summary tab for the robot shop (Applications → Robot Shop → Summary) looks like the screenshot below (there should be a drop in call volume and spikes in erroneous calls and latency).
- Click Events on the sidebar menu and check that there are open incidents, including Sudden increase in the number of erroneous calls on the ‘discount’ service.
2 - Business partners requisition instructions
To request access to the demo environment, email Tim Burke. The turnaround time for requests is two business days.
Click here to go to the Demo script on the next tab.