# [[GOH 08 - Observing an Internet of Things]] [in internal-docs]() <iframe width="560" height="315" src="https://www.youtube.com/embed/" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> Related:: "" Related:: "" ## Talking points - Introductions all around - What does Golioth do? - manages connected devices that vary widely - not just home automation - some things are much more constrained - home: plugged into the wall and using wifi or bluetooth, not size constrained - - What is Internet of Things? - What does this mean? - What does it mean for things to be connected to the internet? Shift from people being online, to things being online on their own - More talking (constant communication) - Need for talking to be comprehensible to humans - Security issues - Fragmentation of protocols and frameworks and devices - From physical to virtual and back - ==efficiency== - No autoscaling - Constrained bandwidth - Constrained pwoer - Responsiveness is tricky to measure accurately - Under the hood of IoT - Protocols (inc. CoAP) - Distributed computing - Low-resource nodes - Industries: not just for home automation - Why is observability important? - Filter out the noise - Transparency and openness about what is being said about us - Management and tracking of everything - Visualisation is important to understand complexity ([[Fast Thinking]] vs [[Slow Thinking]]) - Do you need fast thinking vs slow thinking? - Fat and thin client-server - What parts of observability: metrics, logs, tracing all important. Alerting - Message prioritization - battery vs data? - vs distributed systems like Kubernetes - Kubernetes is actually quite centralized compared to physical devices all over the world. - Strategies for not messing up OTA updates - Have a thin firmware that just knows how to do OTA updates that is in read only memory so it doesn't get deleted. But it does happen - Demo - Create a Golioth account - Install Golioth SDK on device - Features - You can flash new firmware - Stream data bidirectionally - Change device settings per device or per fleet-- you can group devices by: - tags - blueprints - Make RPCs to device - Use Grafana WebSockets plugin to visualize in Grafana - Ultraspeaking - Check out our k6 Office Hours with Dan last week where we talked about how to *test* an internet of things. - Check out Golioth.io, which is an instant IoT cloud that lets you manage your fleet of devices and scale it easily. ## Checklist - [ ] 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! - [ ] 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. - [ ] 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. - [ ] Create a thumbnail. - [ ] Schedule the broadcast on Streamyard, and select the Grafana YouTube channel as the destination. - [ ] In the title, include the instance of Office Hours, i.e. `What's new in Grafana 10? (Grafana Office Hours #01)`. - [ ] Add the standard description as per previous Grafana Office Hours shows. Check the video description and add guests' contact details. - [ ] Get the Streamyard invite link and put it in the "location" of the calendar invite to the guest. - [ ] Get the YouTube link to the show. - [ ] Create an event and announce it on Meetup. - [ ] Schedule a tweet just when the show begins to say "We're live now!" - [ ] Schedule a Slack message on the internal Grafana workspace (in `#general`). - [ ] 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 - [ ] How do you pronounce your name? - [ ] Twitter handles - [ ] We will be using the talking points, but we don't have to be strict about it - [ ] Does anyone want to share their screen? We can do that now, and I can show you how that works - [ ] We'll be streaming to YouTube. - [ ] You'll be able to see comments, but if you have links, I have to paste it into the private chat - [ ] You can also use the private chat if you need to say something, but you can also just say it out loud - [ ] Afterwards, we'll say goodbye to the stream, but please stay on past that - [ ] 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.