# [[GOH 02 - Scenes with Torkel]] [in internal-docs]() <iframe width="560" height="315" src="https://www.youtube.com/embed/pJlWAD5SUYA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> ![[GOH 02 - What is Grafana Scenes.png]] ## Talking points - Who is Torkel? - Co-founder of Grafana Labs, creator of Grafana - Why did you create Grafana in the first place? - The Kibana story - Limitations of Grafana dashboards - Can't build one dashboard where panels have different time ranges to compare multiple periods of time. - Template variables can't be defined for sub-sections - Limited layouts - Static; not great on mobile - Limited grouping - No conditional displays - No drill-down functionality - Lack of framework for developing and sharing dashboards - Dashboards are a JSON file and there's no way to have that automatically update - No API for "creation of dashboard-like experiences and embed those in the app context" - Limited code and dashboard element reuse: you can reuse a panel, but you'd have to re-implement time range picker, refresh button, variables - No custom actions - Apps were already bringing this functionality to Grafana, but app developers had to reimplement a lot of the features. - What does [[Grafana Scenes]] bring? (demo) - Features - For developers - Better [[Separation of Concerns]] - Challenges faced when developing Scenes - hard to handle multiple data source pickers - Had to overwrite some Grafana panels - URL management was a pain - maintaining state for all elements was really difficult - Design consistency was a focus - How can people use Scenes right now? - How to get started with developing for Scenes? - https://github.com/grafana/scenes - https://grafana.github.io/scenes/ - @grafana/scenes on [[Node Package Manager|NPM]] - Look at how to develop an app based on scenes and how it's much easier - Declarative definition of scenes - Future plans for Scenes - When will we move the current dashboards to the Scenes framework? - WYSIWIG editor/builder for Scenes? - Next week: [[David Harris]] is going to join me to talk all about changes to plugins, including how you can use Scenes: [[GOH 03 - Changes to Grafana plugins in Grafana 10 with David Harris]]. ## Timestamps 00:00:00 Torkel Ödegaard and why he created Grafana 00:06:02 Why do we need dynamic dashboards? 00:15:12 What is Scenes? + demo 00:23:23 What is the performance overhead for multiple tabs? 00:24:26 Can you have a panel show depending on the link clicked? 00:25:18 How do you get started with Scenes? 00:29:17 How to create an app with Scenes (code demo) 00:35:39 Can you use Scenes in external freestanding apps? 00:37:40 Is there a roadmap for native support for Scenes in dashboards? 00:42:20 Will Scenes be backwards compatible with legacy dashboards? 00:45:25 Challenges in synchronizing to URL 00:48:19 Where is the documentation on Scenes? 00:50:26 How is Scenes related to the Grafana As Code initiative? 00:52:48 Future plans for Scenes 00:57:07 Is Scenes already usable? 00:58:47 What are some resources for using Scenes? ## Checklist - [x] Contact the guest and tell them about Office Hours. > At Grafana Labs, we do a weekly livestream called Grafana Office Hours, where we have guests on to talk about how to use Grafana, observability, or visualization. I saw your [blog post/video/post] on [source] and I think it would be great to have you on the show to share your experience about [topic]. Office Hours is an hour-long live conversation that is streamed to the [Grafana YouTube channel](https://youtube.com/@grafana). It's very casual, and you can also share your screen if you'd like to do a demo (not required). If you'd like to join, I'd love to have you! - [x] If the guest agrees, choose a date for the Office Hours session. Ask them for a photo you can use for promotion, or ask for permission to use their profile pic on social media. - [x] Invite them to the Grafana Office Hours calendar invite (choose "this instance only", not the whole series). Change the invite to include the episode number and their name, ie `Grafana Office Hours 01 with Mitch`. This is to save the date. - [x] Create a thumbnail. - [x] Schedule the broadcast on Streamyard, and select the Grafana YouTube channel as the destination. - [x] In the title, include the instance of Office Hours, i.e. `What's new in Grafana 10? (Grafana Office Hours #01)`. - [x] Add the standard description as per previous Grafana Office Hours shows. Check the video description and add guests' contact details. - [x] Get the Streamyard invite link and put it in the "location" of the calendar invite to the guest. - [x] Get the YouTube link to the show. - [ ] Create an event and announce it on Meetup. - [x] Schedule a tweet just when the show begins to say "We're live now!" - [x] Schedule a Slack message on the internal Grafana workspace (in `#community`). - [x] Schedule a Slack message on the public Grafana Slack workspace (in `#grafana`) - [ ] Add timestamps to the video (at least four). - [ ] Add any links shared to the description of the video. - [ ] Add the video to video playlists that make sense (at the very least, the "Grafana Office Hours" one.) ### Just before the show - Before the show - [x] How do you pronounce your name? - [x] What are your pronouns? - [x] We will be using the talking points, but we don't have to be strict about it - [x] Does anyone want to share their screen? We can do that now, and I can show you how that works - [x] We'll be streaming to YouTube. - [x] You'll be able to see comments, but if you have links, I have to paste it into the private chat - [x] You can also use the private chat if you need to say something, but you can also just say it out loud - [x] Afterwards, we'll say goodbye to the stream, but please stay on past that - [x] Just in case I disconnect... stall for a minute and I'll be right back. ## Repurposing this content Consider reusing the content in other forms: - Blog post - Order the transcript from [Rev](https://rev.com) and post it on the blog, BUT with headings, subheadings, callouts, and summaries to make it more digestible. Embed the video into the blog post as well. - Shorter video - Edit the video into shorter, tutorial-style video(s) that we can repost and/or embed in documentation. - Docs article - Update any existing documentation.