Podcasts about chronosphere

Hey Podtimists,This week David is on a well earned vacation and so we called in help from our dear friend AJ Fillari! AJ speaks on their experience with a number of fairly new games and Chase opens a meatball store.We also took a deeper look at the new space crafting game, appropriately named SpaceCraft! We were provided codes for this game, thanks to Shiro Games for that! Also thanks so much to AJ for coming on and talking about video games! ---Timestamps:(0:00) - Intro(4:40) - What we've been playing(5:25) - The Lift: Supernatural Handyman Simulator(15:20) - Solarpunk(31:20) - Enter the Chronosphere(42:39) - KuloNiku: Bowl Up!(51:27) - Deep Pixel Melancholy(54:37) - Chivalware(59:46) - AJ's Podtimistic thing of the week(1:03:51) - Chase's Podtimistic thing of the week(1:07:26) - SpaceCraft(1:30:13) - Outro---Games mentioned: The Lift: Supernatural Handyman SimulatorSolarpunkEnter the ChronosphereKuloNiku: Bowl Up!Deep Pixel MelancholyChivalwareSpaceCraft

IGN JAPAN編集部のスタッフが、最近遊んだゲームについて話す番組 00:00 オープニング 00:31 『SILENT HILL: Townfall』 12:18 『Mina the Hollower』 23:58 『Enter the Chronosphere』 ■出演 クラベ・エスラ 野口広志 お茶缶（フリーライター） ■「今週遊んだゲーム」の再生リストはこちら https://www.youtube.com/playlist?list=PL5dP0ylcT42fwUkuleiG6Qrz0NS0sL59- ■「しゃべりすぎGAMER」の再生リストはこちら https://www.youtube.com/playlist?list=PL5dP0ylcT42dJXN_5KJECJ8cI9hK690_e ■ポッドキャスト版 iTunes　https://podcasts.apple.com/jp/podcast/ign-japan-%E3%81%97%E3%82%83%E3%81%B9%E3%82%8A%E3%81%99%E3%81%8Egamer-%E3%83%9D%E3%83%83%E3%83%89%E3%82%AD%E3%83%A3%E3%82%B9%E3%83%88/id1258418439 Spotify　https://open.spotify.com/show/4AKK4MIlRk3Zfj8my703D8?si=x1_N0RZnTWiagXspsoIUkA ■ゲーム＆映画グッズ専門店「IGN JAPAN STORE」 https://ignstore.jp/ ■一部使用楽曲 MusMus：http://musmus.main.jp/ ――――――――――― IGN JAPAN : http://jp.ign.com/ Twitter : https://twitter.com/IGNJapan Facebook : https://www.facebook.com/IGNJapan コメント投稿ルール：http://jp.ign.com/ign-japan/21173/editorial/ign-japanyoutube

Is memory truly cyclical, or has the AI data center boom changed the rules? In Part 2 of the How CSI Invests series, Nick and Kasey tackle one of the most debated questions among semiconductor investors by walking through the investment thesis checklist step that asks: what kind of business cycle does this company actually have?Rather than labeling companies simply cyclical or non-cyclical, the framework breaks businesses into short cycle, long cycle, and non-cyclical categories based on how closely revenue tracks changes in GDP growth. A short cycle business sees revenue move quickly with the economy, while a long cycle or non-cyclical business continues growing steadily regardless of macro conditions. The traditional eleven sectors of the economy do not map cleanly onto this framework, and Nick and Kasey explain why semiconductors, SaaS, telecom carriers, and ad-driven internet platforms can all fall in very different places even within the same official sector.The episode applies this framework to six real companies. Micron is examined as a short cycle business currently in year two of a strong memory upcycle, with historical precedent for these cycles to run several years. Intuitive Surgical is discussed as a long cycle healthcare hardware business tied to product generation launches. Vertex Pharmaceuticals is presented as a genuinely non-cyclical pharmaceutical company with steady growth. NextEra Energy represents the utilities sector and one of the longest cycles of all. Credo Technologies, a newer public company, is evaluated as likely short cycle, with a look at its fiscal 2027 guidance calling for eighty percent revenue growth and fifty percent adjusted profit margins. Finally, Palo Alto Networks is broken down as a cyclical business once acquisitions like CyberArk and Chronosphere are stripped out, with commentary on CEO Nikesh Arora's view that cybersecurity is constantly chasing the next emerging risk.The episode closes with the revenue analysis questions CSI uses for every company: who the primary customers are, whether revenue is concentrated, what is actually being monetized, why customers choose to spend money with that company over alternatives, and what risks could disrupt the business. Understanding these fundamentals is what allows an investor to tune out noisy debates about whether a cycle has "changed forever" and instead build real conviction in a business.For in-depth stock research and the Semiconductor Insider membership,visit chipstockinvestor.com.

The June 2026 Nintendo Direct, Xbox can't make enough Xboxes, and LoL player fined for not hi-fiving. Plus, Pete talks the demo for 1666 Amsterdam, Ruby talks Enter the Chronosphere, and special guest David Smith talks LEGO Batman: Legacy of the Dark Knight.Become a Patron today at: https://www.patreon.com/backpocketCheck us out on Twitch: http://www.twitch.tv/back_pocketFollow @backpocketvids on Twitter, Bluesky, YouTube, TikTok and Instagram!For business: contact@lowkii.tv Hosted on Acast. See acast.com/privacy for more information.

It has been a busy Summer Game Fest and all the events from the State of Play to the Nintendo Direct. This week Willa and Robin dive into what announcements piqued their interest, namely all the ones with vampires (of which there were many). Timestamps:(00:20) Cryptid talk?(02:48) A whole lot of Summer Game Fest week announcements(54:08) What else have Willa and Robin been up to this week? (feat. Moonsigil Atlas, Enter the Chronosphere, Dimension 20: City Council of Darkness) Mentioned this week: Support us on Ko-fi!Check out the network at TheWorstGarbage.online!Join The Worst Garbage Discord!Follow us and send us questions!Follow Robin!Follow Willa!Music Street Food by FASSoundsThings are bad right now, but you can help make them better. Please take some time to consider how you can help trans people, immigrants, and others targeted by our fascist government with this Big List Of Links. Hosted on Acast. See acast.com/privacy for more information.

Microsoft Build 2026 announced an end-to-end agentic AI stack. COMPUTEX Taipei confirmed heterogeneous AI infrastructure across ARM, Marvell, Intel, Qualcomm, and NVIDIA. Alphabet raised $80 billion. Cisco Live repositioned the network as the AI platform. Patrick Moorhead and Daniel Newman break it all down alongside earnings from Broadcom, HPE, Palo Alto Networks, and CrowdStrike, plus the token cost conversation, the edge AI push, and what Palantir and Oracle are saying about proprietary data as the real AI moat. The handpicked topics for this week are: Microsoft Build 2026 Announced an End-to-End Agentic AI Stack: Microsoft shipped MAI-Thinking-1, its first homegrown thinking model, alongside Scout, Microsoft IQ, Project Solara, and a Majorana 2 quantum update targeting a 2029 commercial timeline with claims of a 1,000x reliability gain. Pat describes MAI-Thinking-1 as likely better than Sonnet 4.6 in blind testing and delivering close to GPT 5.5 quality at a far lower cost. Scout is Microsoft's first autopilot agent, anchoring the M365 Agent Suite with Office Pilot Agent Mode and Agent 365. Microsoft IQ serves as the context layer, integrating M365, business data, boundary IQ, and web IQ with GitHub Copilot, Foundry, and Copilot Studio. Project Solara is a new Android-based platform built for agent-first devices across transportation, retail, and hospital settings. Microsoft also added 83 Unix commands to the Windows stack. Dan frames Microsoft's real play as distribution, not frontier model development, noting that the open model ecosystem being pulled into the platform will matter more to CFOs managing token costs at scale. (The Decode) The AI Stack Goes Multi-Silicon — COMPUTEX Taipei 2026 Confirms Heterogeneous AI Infrastructure: ARM's AGI CPU is in production with Google moving its TPU head node to ARM, and adding Oracle and ByteDance as new customers. ARM also introduced a new switch, the TT100, and put the 51T CPO switch on stage. Marvell received a trillion-dollar company endorsement from Jensen Huang, adding $90 billion in market cap on the comment alone. Intel announced disaggregated inference details and Xeon 6+ Clearwater Forest, its first 18A data center processor. Vista Equity and Cambium Capital announced a NeoCloud called Vector Core Compute, with Xeon 6 handling orchestration, Salmonova RUs handling decode, and Blackwell GPUs handling pre-fill. Qualcomm's Cristiano Amon announced the Dragonfly data center brand with Snapdragon C details coming at their June investor day. The WSTS raised the 2026 semiconductor TAM forecast by 90% to $1.51 trillion, with Pat noting the market could hit a trillion dollars if memory is excluded entirely. (The Decode) NVIDIA RTX Spark and the Edge AI Push: NVIDIA coordinated with ARM and Microsoft around the RTX Spark at COMPUTEX, with the shared message being that the future of Windows is here. Signal65's Ryan Shrout asked Jensen directly why NVIDIA wants to be in the PC business, given low margins and diminishing returns. Dan frames the answer in the context of devices increasingly becoming mobile data centers, capable of running models at much greater efficiency than cloud delivery. The edge AI conversation is also directly tied to token cost economics: as intelligence delivery moves closer to the device, the cost per token drops significantly. The jury is still out on whether NVIDIA will meaningfully disrupt the PC market, but its influence over OEMs like Lenovo and Dell that depend on it for data center gives it real leverage over SKUs. (The Decode) Token Economics and Frontier Model Cost Pressure: Dan and Pat discuss a substantive shift in how enterprises are thinking about AI consumption costs. Dan argues that "token maxing," the practice of defaulting to the most powerful frontier model for every task, has now effectively peaked, as bills have come due at scale. Companies paying for tokens in volume are starting to question whether they can afford the prices that frontier models actually cost to deliver. Pat pushes back, saying the dynamic is still present, but both analysts agree that the market is moving toward a model where token selection is matched to the job, with Microsoft's MOE approach and thinking models positioned to help CFOs manage that economics story. (The Decode) Continuum Goes Public at Highest Valuation for an AI Platform: Dan notes that Continuum, the Honeywell-spawned quantum company, went public this week at what he calls the highest valuation for an AI platform to date. He flags that IonQ will likely contest that characterization. The broader context is Microsoft entering the quantum conversation with Majorana 2 at Build, a name that has largely been absent from the quantum race, while IBM has received most of the attention. (The Decode) AI CapEx Has Outgrown Cash Flow — Alphabet's $80 Billion Equity Raise: On June 1, Alphabet announced an $80 billion equity capital raise, upsized to $85 billion, structured as $40 billion ATM, $30 billion underwritten, and a $10 billion private placement with Berkshire Hathaway anchoring. Pat frames the questions over CapEx returns as entirely dependent on whether you are an AI boomer or a doomer: if the payback comes, the raise is the right move. If it does not, the math doesn't close. Dan argues the investment is existential, drawing parallels to how infrastructure-first companies have always spent ahead of monetization, and notes that Google's equity is being used as a capital engine that may be more efficient than the debt markets right now. Both analysts flag the downstream implications for Broadcom, MediaTek, and Marvell given the TPU connection. (The Decode) The Network Becomes the AI Platform: Cisco Live 2026: Cisco launched Silicon One P200, the Secure AI Factory with NVIDIA and Spectrum X, AgenticOps, MCP-native automation, Cisco IQ, LiveProtect, and folded Astrix Security and Galileo into Splunk under one control plane. Pat identifies Cisco Cloud Control as the biggest announcement of the entire show, pulling together Catalyst, Meraki, Nexus, Firewall, and WebEx under agentic ops that run natively through MCP, with code running directly on smart switches that have x86 processors. Pat also credits Cisco for establishing Silicon One as a credible chip alternative for hyperscalers capable of taking on Tomahawk and Jericho. Dan frames the long-term opportunity as campus and branch enablement when industrial AI and robotics deployments accelerate, arguing that the numerator of AI's economic impact has barely started, as edge deployment spending has not yet begun. (The Decode) The Flip: Did Microsoft Build 2026 Effectively End the OpenAI Partnership? Pat argues the divorce decree has been filed. MAI-Thinking-1 was built with zero distillation from third-party models offering clean enterprise data lineage, with Maia 200 in production plus Anthropic chip supply, which signals vendor hedging. OpenAI is going all-in on AWS, which means you cannot be married to two people, and the full Build stack covering model, OS containment via MXC, agents via Scout and Agent 365, and context via Microsoft IQ removes every architectural dependency on OpenAI. Dan counters that Microsoft is hedging rather than leaving and predicts the partnership will run through the decade. Enterprise Copilot customers are explicitly showing in data that they demand GPT 5.5, internal benchmarks have not been independently validated, and Microsoft stands to make meaningful money from the OpenAI IPO. (The Flip) Broadcom Q2 FY26 Earnings: Broadcom posted revenue of $22.19 billion, a narrow miss depending on which consensus data set is used, with EPS of $2.44 beating estimates and AI semis at $10.8 billion. Hock Tan declined to raise the $100 billion full-year AI chip target, and the stock dropped 13% in premarket trading. Q3 guide came in at $29.4 billion. Pat calls the miss a timing issue driven by Google's multi-sourcing across Marvell, MediaTek, and Broadcom rather than a fundamental problem. Dan flags that Hock Tan opened the earnings call by accidentally reading from the 2025 print, calling it "not the best moment." Sell-side re-ratings held in the 500s across Jefferies, Mizuho, and Deutsche Bank despite the drop, with Futurum Equities having it at 600. (Bulls and Bears) Hewlett Packard Enterprise Q2 FY26 Earnings: HPE delivered revenue of $10.68 billion, up 40% year over year, and EPS of $0.79, up 100%. Juniper integration and AI servers both outperformed, and all FY26 guides were raised. The stock jumped 19% after hours before settling into a roughly 15% gain, with HPE up 68% over the last month. Pat frames HPE as a value play rather than a volume play, methodically targeting enterprise and sovereign cloud deals where it can maintain profitability, rather than competing for massive NeoCloud volume. Antonio Neri was clear on the call that the profitability pull-forward is a one-shot deal. Pat and Dan will both be at HPE Discover the week after next to interview Neri and the C-suite. (Bulls and Bears) Palo Alto Networks Q3 FY26 Earnings: Palo Alto posted revenue of $3.0 billion, up 31% year over year, beating the $2.94 billion estimate, with non-GAAP EPS of $0.85, beating the $0.79 to $0.81 range. NGS ARR reached $8.1 billion, up 60% year over year, including $1.6 billion from CyberArk and Chronosphere. RPO hit $18.4 billion, up 36%. Both FY26 revenue and EPS guides were raised. Adjusted FCF margin came in at 38.5% TTM, up 430 basis points. The stock jumped 11% immediately after hours, then drifted lower. Pat points to 2,200 platformized customers and 120% net retention as the most important metrics. Dan notes the SaaSpocalypse thesis continues to be wrong. (Bulls and Bears) CrowdStrike Q1 FY27 Earnings and the Proprietary Data Moat Argument: CrowdStrike posted revenue of $1.39 billion with EPS of $1.10 and ARR of $5.51 billion. Net new ARR of $255.8 million set a Q1 record, up 32% year over year. FY27 net new ARR guide was raised by $52 million to a $1.29 billion midpoint, and FY27 revenue was raised to $5.915 to $5.959 billion. A 4-for-1 stock split was announced effective July 2nd. The stock dropped 11% despite the beat after a 64% year-to-date run into earnings. Dan uses the results to make a broader argument against the software disruption thesis, referencing Palantir CEO Alex Karp daring customers to build without him using Anthropic or OpenAI, and Larry Ellison's argument that the real AI value unlock sits in proprietary enterprise data that is not accessible to frontier models. Enterprises with governed, secure, proprietary data will continue to need platforms like CrowdStrike regardless of what frontier models can do. (Bulls and Bears) Six Five Summit is coming. Salesforce CEO Mark Benioff will kick off the event. Register and stay current at sixfivemedia.com/summit. Watch the full video at sixfivemedia.com, and be sure to subscribe to our YouTube channel so you never miss an episode.   The Decode Microsoft Declares Independence — Build 2026 Ships an End-to-End Agentic AI Stack (MAI-Thinking-1 + Scout + Microsoft IQ + Project Solara + Majorana 2) https://www.theverge.com/tech/941738/microsoft-build-2026-biggest-announcements The AI Stack Goes Multi-Silicon — Computex 2026 Confirms a Heterogeneous AI Infrastructure (ARM + Marvell + Intel ASIC + Qualcomm + RTX Spark); WSTS Raises 2026 Semi TAM Forecast 90% to $1.51T https://www.tomshardware.com/tag/computex AI Capex Has Outgrown Cash Flow — Alphabet's $80B Equity Raise Is the Largest in U.S. Corporate History; Berkshire Anchors $10B https://abc.xyz/investor/news/news-details/2026/Alphabet-Announces-Proposed-80-Billion-Equity-Capital-Raise-to-Expand-AI-Infrastructure-and-Compute-2026-b0myAMewCa/default.aspx The Network Becomes the AI Platform — Cisco Live 2026 Launches Silicon One P200, Secure AI Factory (with NVIDIA), AgenticOps, Astrix Security + Galileo https://www.cisco.com/site/us/en/about/whats-new/index.html The Flip Did Microsoft Build 2026 Effectively End the OpenAI Partnership? MAI-Thinking-1 Beats Sonnet 4.6 in Blind Testing, Microsoft Claims GPT-5.5 Parity at 10x Cost Efficiency — Will MS Quietly Wind Down OpenAI Exclusivity by FY28, or Is OpenAI Still the Frontier Anchor Microsoft Needs?   FOR:  MAI-Thinking-1 beating Sonnet 4.6 in blind preference + GPT-5.5 parity at 10x cost efficiency is a frontier-model independence proof point https://www.latent.space/p/ainews-microsoft-build-mai-thinking Build 2026: Accumulating Evidence of Microsoft's AI Independence — EDN (June 4) — https://www.edn.com/build-2026-accumulating-evidence-of-microsofts-ai-independence/ Maia 200 in production + Anthropic-Maia chip talks signal Microsoft is hedging its inference vendor stack https://blogs.microsoft.com/blog/2026/01/26/maia-200-the-ai-accelerator-built-for-inference/ Microsoft canceled Anthropic's internal software licenses + pivoted to chip-supply pursuit — customer-not-competitor positioning https://www.cnbc.com/2026/05/21/anthropic-microsoft-maia-200-ai-chip.html   AGAINST:  Enterprise Copilot customers explicitly demand GPT-5.5 — internal benchmarks don't replace the brand https://learn.microsoft.com/en-us/microsoft-365/copilot/release-notes?tabs=all MAI-Thinking-1 benchmarks haven't been third-party verified — Microsoft is the only source https://www.latent.space/p/ainews-microsoft-build-mai-thinking The MS-OpenAI partnership is contractual through 2030+ — unwinding it is impractical and expensive https://blogs.microsoft.com/blog/2026/04/27/the-next-phase-of-the-microsoft-openai-partnership/ Microsoft's actual strategic risk is OpenAI leaving, not MS leaving — Anthropic + OpenAI IPOs make OpenAI exit risk the real concern https://www.anthropic.com/news/confidential-draft-s1-sec Bulls & Bears Broadcom (AVGO) Q2 FY26 ACTUALS — Rev $22.19B (Narrow Miss) + EPS $2.44 (Beat); AI Semis $10.8B; Hock Tan Refuses to Raise the $100B Full-Year AI Chip Target — Stock −13% Premarket; Q3 Guide $29.4B https://www.cnbc.com/2026/06/03/broadcom-avgo-earnings-report-q2-2026.html Hewlett Packard Enterprise (HPE) Q2 FY26 ACTUALS — Blowout: Rev $10.68B (+40%), EPS $0.79 (+100%); Juniper Integration + AI Servers Both Outperform; FY26 Guides All Raised; Stock +19% AH https://www.businesswire.com/news/home/20260601866494/en/HPE-Reports-Fiscal-2026-Second-Quarter-Results Palo Alto Networks (PANW) Q3 FY26 ACTUALS — Beat-and-Raise: Rev $3.0B (+31% YoY, Beat $2.94B), Non-GAAP EPS $0.85 (Beat $0.79-0.81); NGS ARR $8.1B (+60% YoY, $1.6B from CyberArk + Chronosphere); RPO $18.4B (+36%); FY26 Revenue + EPS Guides BOTH RAISED; Adj FCF Margin 38.5% TTM (+430 bps); Stock +11% Immediate AH, Then Drifted Lower https://www.paloaltonetworks.com/company/press/2026/palo-alto-networks-reports-fiscal-third-quarter-2026-financial-results CrowdStrike narrowly beats estimates on AI tailwinds, but stock falls 9% — CNBC (June 3) — https://www.cnbc.com/2026/06/03/crowdstrike-crwd-q1-2027-earnings.html  

On a jam-packed episode of the Crewcast, all 5 regular members join to discuss Paralives, Vampire Crawlers, Running Train, Mina the Hollower, Mixtape, Enter the Chronosphere, Carrot Kingdom, and more! Paralives: https://store.steampowered.com/app/1118520/Paralives/ RUNNING TRAIN: https://store.steampowered.com/app/4630570/RUNNING_TRAIN/ Vampire Crawlers: https://store.steampowered.com/app/3265700/Vampire_Crawlers_The_Turbo_Wildcard_from_Vampire_Survivors/ Forza Horizon 6: https://store.steampowered.com/app/2483190/Forza_Horizon_6/ Enter the Chronosphere: https://store.steampowered.com/app/1969810/Enter_the_Chronosphere/ Mina the Hollower: https://store.steampowered.com/app/1875580/Mina_the_Hollower/ Making of Mina the Hollower: https://www.youtube.com/watch?v=Z6WWGkVf3uU Mixtape: https://store.steampowered.com/app/2582320/Mixtape/ Carrot Kingdom (PICO-8): https://www.lexaloffle.com/bbs/?tid=156882 Carrot Kingdom (Atari 2600, not the same game at all): https://carrotkingdom.net/download.html iTunes Page: https://itunes.apple.com/us/podcast/noclip/id1385062988 RSS Feed: http://noclippodcast.libsyn.com/rss Spotify: https://open.spotify.com/show/5XYk92ubrXpvPVk1lin4VB?si=JRAcPnlvQ0-YJWU9XiW9pg Watch our docs: https://youtube.com/noclipvideo Crewcast channel: https://www.youtube.com/channel/noclippodcast Follow our games coverage escapades: https://www.youtube.com/@Noclip2 Learn About Noclip: https://www.noclip.video Become a Patron and get early access to new episodes: https://www.patreon.com/noclip Chapters: 0:00:00 - Intro 0:08:37 - Thanking our Patreon supporters! 0:12:21 - Paralives 0:33:03 - RUNNING TRAIN | 走ル列車！ 0:42:12 - Vampire Crawlers 0:48:54 - Forza Horizon 6 0:51:41 - Enter the Chronosphere 0:59:52 - Mina the Hollower 1:09:17 - Mixtape 1:21:09 - Carrot Kingdom 1:26:43 - Q: Has anyone played Banishers: Ghosts of New Eden? 1:29:35 - Q: What games have you bought with 0 foreknowledge? 1:37:08 - Q: What are some niche games with dedicated audiences? 1:42:43 - Noclip Updates 

After a quick look at Enter the Chronosphere https://shorturl.at/jFXQj we dive into the world of Psygnosis's WipEout series: the techno tracks, Designer's Republic aesthetic, and the high speed anti-grav brilliance of it all. SHOWNOTES: 00:10 - Intro 03:15 - Enter the Chronosphere https://shorturl.at/jFXQj 08:16 - MHG Chat: Wip3out Special Edition 13:15 - Wipeout: the Amiga connection 15:14 - Psygnosis & The Designer's Republic 19:05 - Presentation & ageing out of the zeitgeist? 21:26 - F1 & the in-game aesthetic 23:40 - The UK release of WipEout 25:18 - Modern emulation options 26:23 - The British angle: post-Thatcher reflection 29:42 - Children of Feisar: modern AG alternatives 34:15 - Outro

Jeff and Christian welcome youtuber and game reviewer Tamoor Hussain back to the show this week to discuss reports that FROM Software prevented Bloodborne remake from happening, Insomniac's Marvel's Wolverine getting a September release date, and a new rhythmn game from the folks who made Guitar Hero.The Playlist:Tamoor: Resident Evil Requiem, AYN Thor, ClutchtimeChristian: Resident Evil Requiem; Marathon Server Slam: Open PreviewJeff: Resident Evil: Requiem, Steam Next Fest Demos (best of the best): Vampire Crawlers, Enter the Chronosphere, Spellsy, Alabaster Dawn, Rune Dice, Croak, TMNT: Empire CityParting Gifts!

Featuring: Michael "Boston" Hannon and Paul "Moonpir" Smith Running Time: 1:19:23 Video Version: YouTube For this episode of TVGP's Critical Misses we're finally at the big one: The Flash. Join us as we chat about origin stories, remembering our favorite Batman, saving babies, The Chronosphere, Emo Flash, our love of the Flash TV show, and much, much more! Applause sound effect from SoundBible Royalty free music from https://www.fesliyanstudios.com Become a patron of TVGP for just a few dollars a month at E1M1's Patreon Page! Get two month early access to Critical Misses, uncensored outtakes, production meetings, and much more for just $5/month!

Is it time to look past the AI bubble and focus on the infrastructure actually securing it? Today, we're pivoting to a top secular growth trend: Cybersecurity.With the industry projected to grow 12% annually and hit $215 billion in spending by 2025, Palo Alto Networks (PANW) is making aggressive moves to dominate the landscape. We discuss their M&A strategy—including the purchase of Chronosphere and the pending CyberArk deal—and what this means for their entry into the cloud observability market against competitors like Datadog and Dynatrace.In this video, we cover:-- AI-Native Security: Why AI agents and cloud workloads are driving the next wave of IT spending.--The Financials: a breakdown of PANW's cash pile, revenue acceleration, and rising stock-based compensation.-- Valuation Check: With the stock trading around 30-33x Free Cash Flow, is Palo Alto Networks a buy, a hold, or just fair value?.We analyze whether this cybersecurity giant can execute on its "platformization" strategy and if the recent sell-off offers a prime entry point for investors.Tickers mentioned: PANW,CYBR,DT,DDOG#PaloAltoNetworks #Cybersecurity #StockMarket #Investing #PANW #CloudSecurity #AIStocksJoin us on Discord with Semiconductor Insider, sign up on our website: www.chipstockinvestor.com/membershipCharts & Data provided by fiscal.ai. Get 25% off any paid plan (Nov 26 - Dec 1) using our link: https://fiscal.ai/csi/Sign Up For Our Newsletter: https://mailchi.mp/b1228c12f284/sign-up-landing-page-short-formIf you found this video useful, please make sure to like and subscribe!*********************************************************Affiliate links that are sprinkled in throughout this video. If something catches your eye and you decide to buy it, we might earn a little coffee money. Thanks for helping us (Kasey) fuel our caffeine addiction!Content in this video is for general information or entertainment only and is not specific or individual investment advice. Forecasts and information presented may not develop as predicted and there is no guarantee any strategies presented will be successful. All investing involves risk, and you could lose some or all of your principal.Nick and Kasey own shares of Palo Alto Networks

Take a Network Break!  We start with a relative path traversal vulnerability in Fortinet’s FortiWeb.  We’ll move on to an acquisition by Palo Alto Networks, another hiccup from our friends at Cloudflare, some AI announcements by Itential and Gluware, and finish with first quarter 2026 fiscal results from Palo Alto Networks. AdSpot Sponsor: Itential  ... Read more »

Take a Network Break!  We start with a relative path traversal vulnerability in Fortinet’s FortiWeb.  We’ll move on to an acquisition by Palo Alto Networks, another hiccup from our friends at Cloudflare, some AI announcements by Itential and Gluware, and finish with first quarter 2026 fiscal results from Palo Alto Networks. AdSpot Sponsor: Itential  ... Read more »

Take a Network Break!  We start with a relative path traversal vulnerability in Fortinet’s FortiWeb.  We’ll move on to an acquisition by Palo Alto Networks, another hiccup from our friends at Cloudflare, some AI announcements by Itential and Gluware, and finish with first quarter 2026 fiscal results from Palo Alto Networks. AdSpot Sponsor: Itential  ... Read more »

Western Digital (WDC) has more room to run, according to BofA. Diane King Hall explains the firm's price target hike and why hard disk drive demand is a key piece to its bullish outlook. Palo Alto Networks (PANW) slid slightly to the downside despite posting strong earnings and guidance. Investors appear to have questions around the company's $3.35 billion acquisition of Chronosphere. In the retail space, Diane notes the massive post-earnings sell-off in Bath & Body Works (BBWI). ======== Schwab Network ========Empowering every investor and trader, every market day.Options involve risks and are not suitable for all investors. Before trading, read the Options Disclosure Document. http://bit.ly/2v9tH6DSubscribe to the Market Minute newsletter - https://schwabnetwork.com/subscribeDownload the iOS app - https://apps.apple.com/us/app/schwab-network/id1460719185Download the Amazon Fire Tv App - https://www.amazon.com/TD-Ameritrade-Network/dp/B07KRD76C7Watch on Sling - https://watch.sling.com/1/asset/191928615bd8d47686f94682aefaa007/watchWatch on Vizio - https://www.vizio.com/en/watchfreeplus-exploreWatch on DistroTV - https://www.distro.tv/live/schwab-network/Follow us on X – https://twitter.com/schwabnetworkFollow us on Facebook – https://www.facebook.com/schwabnetworkFollow us on LinkedIn - https://www.linkedin.com/company/schwab-network/About Schwab Network - https://schwabnetwork.com/about

Palo Alto Networks announced on Wednesday that it was acquiring Chronosphere for $3.35 billion to boost its AI-enabled cybersecurity offerings. Palo Alto CEO Nikesh Arora tells Bloomberg's Ed Ludlow that the acquisition of Chronosphere put the company “smack in the middle of where the market is going.”See omnystudio.com/listener for privacy information.

Wall Street slumped late in the session with the S&P 500 erasing a 2% gain as Nvidia led the sector lower. Nvidia turned negative, unwinding its post-earnings rally, while Palo Alto Networks announced plans to acquire Chronosphere. Walmart lifted its outlook, and U.S. data showed solid September job gains even as the unemployment rate ticked higher. In commodities, oil dipped on renewed hopes for a Ukraine–Russia peace plan, gold fell as strong U.S. jobs data dimmed the prospects of a December rate cut, and iron ore retreated on supply-glut concerns. Back home, Aussie shares are expected to drop amid a spike in volatility, while a risk-off tone weighs on the Aussie dollar. The content in this podcast is prepared, approved and distributed in Australia by Commonwealth Securities Limited ABN 60 067 254 399 AFSL 238814. The information does not take into account your objectives, financial situation or needs. Consider the appropriateness of the information before acting and if necessary, seek appropriate professional advice.See omnystudio.com/listener for privacy information.

While Nvidia (NVDA) undeniably drew most investors' attention after hours, Datavault AI's Nathaniel Bradley turns to Palo Alto Networks' (PANW) earnings to explain why the company saw downside action after its beat and guidance raise. He attributes the selling to Palo Alto's $3.35 billion acquisition of Chronosphere. Nathaniel explains how the evolution of A.I. pushed Palo Alto to make the acquisition and A.I.'s impact on the cybersecurity space. ======== Schwab Network ========Empowering every investor and trader, every market day.Options involve risks and are not suitable for all investors. Before trading, read the Options Disclosure Document. http://bit.ly/2v9tH6DSubscribe to the Market Minute newsletter - https://schwabnetwork.com/subscribeDownload the iOS app - https://apps.apple.com/us/app/schwab-network/id1460719185Download the Amazon Fire Tv App - https://www.amazon.com/TD-Ameritrade-Network/dp/B07KRD76C7Watch on Sling - https://watch.sling.com/1/asset/191928615bd8d47686f94682aefaa007/watchWatch on Vizio - https://www.vizio.com/en/watchfreeplus-exploreWatch on DistroTV - https://www.distro.tv/live/schwab-network/Follow us on X – https://twitter.com/schwabnetworkFollow us on Facebook – https://www.facebook.com/schwabnetworkFollow us on LinkedIn - https://www.linkedin.com/company/schwab-network/About Schwab Network - https://schwabnetwork.com/about

THIS PODCAST IS DEDICATED TO THE BRAVE MUJAHIDEEN FIGHTERS OF AFGHANISTAN. This datatrack contains discussion of the following topics; classic 80s racism, Megatron's canny involvement in geopolitics, cars = planes, the Giant Purple Griffin, Fireflight continues to be nobody, Slingshot's problematic views, the CHRONOSPHERE, Orion Pax's weird vibes, who the fuck is Dion, time loops, Optimus' transition into a more mythic figure, and questioning how you air an episode THIS out of order. Noise Space | Discord | Patreon This podcast is powered by Pinecast.

We are overdue for a vendor neutral industry wide event dedicated to our favorite topic - open observability.Last month (June 2025) the Cloud Native Computing Foundation (CNCF) ran the first-ever Open Observability Summit, bringing together the world's best experts in the field in a day packed with talks from project maintainers, end users and practitioners.We're proud partners of the event, and are here to bring you the highlights from this industry-shaping event.This special episode has two parts, one recorded onsite before the event, covering conference goals, and insights from the talk submissions, and the other recorded after the event, covering the highlights of the events and the talks. The guests for is episode are two observability veterans: Alok Bhide, member of the event's content committee and head of product innovation at Chronosphere; and Henrik Rexed, developer advocate at Dynatrace, CNCF Ambassador, and host of Is It Observable podcast.Catch up on everything you need to know from the first-ever Open Observability Summit.You can read the recap post: https://medium.com/p/d42c8826d6a5/Show Notes:00:00 - intro02:52 - Part 1 pre-event03:40 - guest intro Alok Bhide04:49 - a new community event for open observability06:58 - talk submission highlights from the CFP content reviewer12:34 - a view of the open observability stack and its use 16:42 - Fluent Bit alignment with OpenTelemetry20:08 - AI in observability25:34 - Part 2 talk highlights26:22 - Fluent Bit vs. OpenTelemetry Collector benchmark analysis37:51 - OpenSearch 3.1 release40:47 - eBay's observability talk47:00 - Kotlin SDK for OTel talk for Android developers51:45 - Otel Collector fine-tuning talk53:52 - Broadcom OTel use case from mobile to mainframe56:43 - Spotify migration from in-house TSDB to VictoriaMetrics and Prometheus58:20 - OTel Collector replacement in Rust with the Rotel project1:00:58 - Noisy neighbors network observability1:03:04 - rising awareness of OTel semantic conventions 1:05:50 - outro Resources:Open Observability Summit + OTel Community Day: https://events.linuxfoundation.org/open-observability-summit-otel-community-day/eBay innovation with open source observability: https://www.youtube.com/watch?v=6ycNhzRVSbU&list=PLj6h78yzYM2NFT2PGItX2idBf7v8fHcy7&index=35 More on eBay's journey to planet-scale observability: https://www.youtube.com/watch?v=-UsU3nRglhA&list=PLd57eY2edRXz4djMETYTm-2p8WGTdoX3D Spotify talk: https://www.youtube.com/watch?v=87koDlpKDR4&list=PLj6h78yzYM2NFT2PGItX2idBf7v8fHcy7Kotlin SDK for OTel: https://www.youtube.com/watch?v=di5nhYvUh6w&list=PLj6h78yzYM2NFT2PGItX2idBf7v8fHcy7More on mobile observability with OTel: https://medium.com/p/2eb847c41941 OpenTelemtry Collector vs. Fluent Bit: https://www.youtube.com/watch?v=tZho5W9L_Z8&list=PLj6h78yzYM2NFT2PGItX2idBf7v8fHcy7&index=8Telemetry Pipelines: https://www.youtube.com/watch?v=0d1g5ZWAc1Y&list=PLj6h78yzYM2NFT2PGItX2idBf7v8fHcy7&index=30 OTel Collector in Rust with Rotel: https://www.youtube.com/watch?v=xeQnP8Ct7qY&list=PLj6h78yzYM2NFT2PGItX2idBf7v8fHcy7&index=16 Rotel project repo: https://github.com/streamfold/rotel  Noisy neighbor detection: https://www.youtube.com/watch?v=xVqiOtXTEFA Socials:BlueSky: https://bsky.app/profile/openobservability.bsky.socialTwitter: ⁠https://twitter.com/OpenObserv⁠LinkedIn: https://www.linkedin.com/company/openobservability/YouTube: ⁠https://www.youtube.com/@openobservabilitytalks⁠Dotan Horovits============Twitter: https://twitter.com/horovits LinkedIn: https://www.linkedin.com/in/horovits/ BlueSky: https://bsky.app/profile/horovits.bsky.social Mastodon: https://fosstodon.org/@horovitsHenrik Rexed===========LinkedIn: https://www.linkedin.com/in/hrexed/BlueSky: @hrexed.bsky.socialYouTube: https://www.youtube.com/@isitobservable Alok Bhide=========LinkedIn: https://www.linkedin.com/in/albhide/

I love the movie City Slickers.If you're unfamiliar, Billy Crystal is a Manhattanite, has a midlife crisis, and goes out West on a cattle drive to try to figure life out.Spoiler alert, the crusty old cowboy teaches him that the secret to life is – ‘One thing. Just one thing. You stick to that and everything else don't mean shhh…” Well, you get the idea.It struck me that this is a great brand lesson as well. You've seen the stats – our ideal customer simply gets hammered with messages every day. And there are so many things your internal team could work on. How to break through the noise? How to prioritize? I love what my next guest told me – “If you don't have one clear position of who you are and why they should care, you're just throwing spaghetti at a wall.”To hear the story behind that lesson, along with many more lesson-filled stories, I sat down with Margaret Dawson, CMO, Chronosphere [https://chronosphere.io/].Chronosphere has raised $343 million in three rounds. In its Series C round in 2023, the company was valued at $1.6 billion.Dawson leads global marketing efforts at Chronosphere, overseeing a budget of $12 million and a team of 23 working on digital experience, corporate communications, demand generation, customer marketing, ABM, Marketing Ops, and Product Marketing.Lessons from the things she madeIf you don't have one clear position of who you are and why they should care, you're just throwing spaghetti at a wallSometimes you need to poke the snakeIntegrated marketing moves the needleMentoring is a two-way streetJust because you can do something doesn't mean you shouldDon't focus so much on winning each battle that you lose the warIf you channeled the characteristics that made you so competent and made you authentically you, you would have the greatest powerWe do not serve ourselves or the world by hiding our light or being afraid to stand tallDiscussed in this episodeJoin us on July 30th at 2 pm EDT for AI Hackathon: Build a powerful lead gen agent in just 90 minutes [https://join.meclabsai.com/mec-050-masterclass] (from MeclabsAI, MarketingSherpa's parent company).Outside-In Messaging: Nothing counts more than the language of the customer (podcast episode #75) [https://marketingsherpa.com/article/interview/outside-in-messaging]The 4 Pillars of Email Marketing [https://sherpablog.marketingsherpa.com/email-marketing/4-pillars-email-summit-2014/]Building Brands: People and culture matter a lot, mentorship matters even more, product matters the most (podcast episode #119) [https://marketingsherpa.com/article/interview/brands]Marketing Campaigns: Lose the brand ego and lean into humility (podcast episode #130) [https://marketingsherpa.com/article/interview/marketing-campaigns]Get more episodesSubscribe to the MarketingSherpa email newsletter [https://www.marketingsherpa.com/newsletters] to get more insights from your fellow marketers. Sign up for free if you'd like to get more episodes like this one.For more insights, check out...TApply to be a guestIf you would like to apply to be a guest on How I Made It In Marketing, here is the podcast guest application – https://www.marketingsherpa.com/page/podcast-guest-application

In this episode of East Coast Elite, Simon Kouttis and Ollie Kuehne sit down with Martin Mao, co-founder and CEO of Chronosphere. From his early days at Uber to founding one of the most disruptive startups in observability, Martin shares what it takes to navigate uncertainty, build conviction, and win at scale. We dive into the mindset shifts behind leaving a tech giant to build something bold, how Martin sees the future of observability, and what it means to lead with clarity in a rapidly evolving market. If you're a founder, engineer, or operator seeking real insights from a builder at the top, this one's for you. Key Topics Covered 00:00 Intro 02:10 What Makes a Strong Founder 04:48 Why Martin Left Uber 09:22 Founding Chronosphere 13:41 Competing with Industry Giants 19:05 The Startup Learning Curve 26:38 Early GTM Decisions 33:20 Scaling with Intent 39:40 Balancing Vision and Feedback 46:14 Leadership Lessons in Hypergrowth 50:12 What's Next for Chronosphere 52:49 Closing Reflections   3 Biggest Lessons Leaving comfort for conviction: Martin's leap from Uber shows that bold moves start with internal clarity, not external certainty. Product-market fit is just the beginning: Real traction comes from execution, team culture, and continuous iteration. Disruption requires ruthless focus: Be crystal clear on who you serve and why your product matters—then say no to everything else. Thanks for listening! This episode was hosted by Simon Kouttis and Ollie Kuehne, founders of Hunters & Unicorns. If you enjoyed this episode, please drop a like/share and subscribe to our channel! Connect with Hunters & Unicorns Website: http://huntersandunicorns.com Twitter:   / huntersun1corns   Instagram:   / huntersandunicorns   Blog: http://huntersandunicorns.com/blog   Notable Quotes “You don't need to have all the answers before you start.” “It's not about being better—it's about being different in a meaningful way.” “Startups work when you're solving real pain, not just building cool tech.” This episode is sponsored by SELR & PG:ai   #softwaresales #huntersandunicorns #playbookuniverse

Martin Mao is the co-founder and CEO of Chronosphere, an observability platform built for the modern containerized world. Prior to Chronosphere, Martin led the observability team at Uber, tackling the unique challenges of large-scale distributed systems. With a background as a technical lead at AWS, Martin brings unique experience in building scalable and reliable infrastructure. In this episode, he shares the story behind Chronosphere, its approach to cost-efficient observability, and the future of monitoring in the age of AI.What you'll learn:The specific observability challenges that arise when transitioning to containerized environments and microservices architectures, including increased data volume and new problem sources.How Chronosphere addresses the issue of wasteful data storage by providing features that identify and optimize useful data, ensuring customers only pay for valuable insights.Chronosphere's strategy for competing with observability solutions offered by major cloud providers like AWS, Azure, and Google Cloud, focusing on specialized end-to-end product.The innovative ways in which Chronosphere's products, including their observability platform and telemetry pipeline, improve the process of detecting and resolving problems.How Chronosphere is leveraging AI and knowledge graphs to normalize unstructured data, enhance its analytics engine, and provide more effective insights to customers.Why targeting early adopters and tech-forward companies is beneficial for product innovation, providing valuable feedback for further improvements and new features. How observability requirements are changing with the rise of AI and LLM-based applications, and the unique data collection and evaluation criteria needed for GPUs.Takeaways:Chronosphere originated from the observability challenges faced at Uber, where existing solutions couldn't handle the scale and complexity of a containerized environment.Cost efficiency is a major differentiator for Chronosphere, offering significantly better cost-benefit ratios compared to other solutions, making it attractive for companies operating at scale.The company's telemetry pipeline product can be used with existing observability solutions like Splunk and Elastic to reduce costs without requiring a full platform migration.Chronosphere's architecture is purposely single-tenanted to minimize coupled infrastructures, ensuring reliability and continuous monitoring even when core components go down.AI-driven insights for observability may not benefit from LLMs that are trained on private business data, which can be diverse and may cause models to overfit to a specific case.Many tech-forward companies are using the platform to monitor model training which involves GPU clusters and a new evaluation criterion that is unlike general CPU workload.The company found a huge potential by scrubbing the diverse data and building knowledge graphs to be used as a source of useful information when problems are recognized.Subscribe to Startup Project for more engaging conversations with leading entrepreneurs!→ Email updates: ⁠https://startupproject.substack.com/⁠#StartupProject #Chronosphere #Observability #Containers #Microservices #Uber #AWS #Monitoring #CloudNative #CostOptimization #AI #ArtificialIntelligence #LLM #MLOps #Entrepreneurship #Podcast #YouTube #Tech #Innovation

In order to clear their names in the eyes of Sigil's more powerful factions, the detectives of Open and Shut must steal from the Dead themselves. Information is gathered, every boon is called in, and the Mortuary looms as the Chronosphere beckons. They cannot fail, but do they have the brains to succeed?---Our show contains fantasy violence (and the occasional foul language), treat us like a PG-13 program!---Kyana and Finbar Pin Pack Available Now! Presale has been extended for one week, preorder for yourself at:https://crowdmade.com/collections/rolling-with-difficultySpecial Thank You to Our Friends at 5 GMs in a Trenchcoat! Check Them Out:https://www.5gmsinatrenchcoat.com/Instagram: @5gmsinatrenchcoatThreads: @5gmsinatrenchcoatTwitter: @5GMsOfficialBlueSky: @5gmsofficial.bsky.socialTik Tok: @5gmsinatrenchcoatSpecial Thank You to Our Friends at Twice Rolled Tales:https://linktr.ee/twicerolledtaleshttps://www.twicerolledtales.com/YouTube: https://www.youtube.com/@twicerolledtalesBlueSky: @twicerolledtales.bsky.socialRolling with Difficulty Patreon:patreon.com/rollingwithdifficultyRolling with Difficulty Discord:https://discord.gg/6uAycwAhy6Merch:Redbubble: https://www.redbubble.com/people/RWDPodcast/shop?asc=uContact the Pod:rollwithdifficulty@gmail.comTwitter: @rollwdifficultyInstagram: @rollwithdifficultyRSS Feed: https://rollingwithdifficultypod.transistor.fm/Youtube: https://www.youtube.com/c/RollingwithDifficultyTik Tok: @rollwithdifficultyBlueSky: @rollwithdifficulty.bsky.socialCast:Dungeon Master - Austin FunkTwitter: @atthefunkThe Set's Journal of Faerun: https://www.dmsguild.com/product/345568/The-Sets-Journal-of-Faerun-Vol-1?term=the+setBlueSky: @atthefunk.bsky.socialBileyg - OSP RedTwitter: @OSPyoutubeInstagram: @overly.sarcastic.productionsOverly Sarcastic Productions: https://www.youtube.com/c/OverlySarcasticProductionsChannel/Ingrid -  Sophia RicciardiTwitter: @sophie_kay_Instagram: @_sophie_kayMoviestruck: https://moviestruck.transistor.fm/Patreon: https://www.patreon.com/moviestruckBlueSky: @sophiekay.bsky.socialFally - LinnieInstagram: @linnieschell@linnieschell on all platformsOobtaglor - NoirTwitter: @NoirGalaxiesBlueSky: @noirgalaxies.bsky.socialWant to send us snail mail? Use this Address:Austin Funk1314 5th AvePO Box # 1163Bay Shore NY 11706Character Art by @stuckinspaceBackground Art by @tanukimi.sMusic by: Dominic Ricciardihttps://soundcloud.com/dominicricciardimusicFeatured Tracks:Open and Shut ThemeBig DowntimeInvestigation ThemeMysterious ThemeTense MomentFinal BattleCity of Doors Theme ★ Support this podcast on Patreon ★

Background Music for Sleep, Meditation, Relaxation, Massage, Yoga, Studying and Therapy …… Hi everyone, this is Jim Butler and welcome to the Deep Energy Podcast 1929 to 1932 - Chronosphere - Parts 1 - 4 Please remember to turn on automatic downloads, like and subscribe, tell a friend, share with your family and leave a review. All of those things help build the podcast. Thank you so much!! ………. This podcast is ad supported. We try the best we can to keep all of the ads at the front and the back of the podcast, but depending on the length of the podcast, there maybe ads in the middle. Please check my Bandcamp page for ad free podcasts. www.jimbutler.bandcamp.com ……………………….. Watch me play live on TikTok @jimbutlermusic or On the Insight Timer App as Jim Butler Links for all of the podcasts in the Deep Energy Podcast Network: Deep Energy Podcast (Current Episodes) https://podcasts.apple.com/us/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga/id511265415 https://open.spotify.com/show/1DhN56DzDKc0FhQqR23v9c Deep Energy Classics - All of the ORIGINAL Episodes  https://podcasts.apple.com/us/podcast/deep-energy-classics-original-episodes/id1734274408 https://www.spreaker.com/podcast/deep-energy-classics-original-episodes--6108618 https://open.spotify.com/show/7BjEFnqcyKWUkHcYdtFS25?si=05aeab39b5bc4a00 Deep Energy Daily Affirmations - Daily Affirmations to get you through the day https://podcasts.apple.com/us/podcast/deep-energy-daily-affirmations/id1729162791 https://open.spotify.com/show/0oaA8dRsWDQLkqeXmykGvu?si=461c7b47417b4e55 Deep Energy Guided Meditations - Guided Meditations to help through your day https://podcasts.apple.com/us/podcast/deep-energy-guided-meditations-with-michelle-davis-jim/id1732674561 https://open.spotify.com/show/1Kg2LTaFux10Ul94phybp8?si=ebbbf33757d64c13 https://www.spreaker.com/podcast/deep-energy-guided-meditations-with-michelle-davis-jim-butler--6098026 Slow Piano for Sleep - Solo Piano Pieces https://podcasts.apple.com/us/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and/id1626828397 https://www.spreaker.com/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and-relaxation--5572963 ………… www,jimbutlermusic.com jimbutlermusic@gmail.com All Social Media (FB - IG - YT - TT) is: @jimbutlermusic Merch: www.deepenergy.threadless.com Bandcamp Monthly No Ads Subscription/Patreon: www.jimbutler.bandcamp.com Custom Made Music: jimbutlermusic@gmail.com ………………….. Thank you for listening. All music is created, performed and composed by Jim Butler. AI IS NEVER USED TO CREATE MY MUSIC. Until the next time, please be kind to one another, peace, bye… …….. Original Image by the Dream App (not sponsored) or Canva (not sponsored) …………………. Become a supporter of this podcast: https://www.spreaker.com/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga-and-studying--4262945/support.

Background Music for Sleep, Meditation, Relaxation, Massage, Yoga, Studying and Therapy …… Hi everyone, this is Jim Butler and welcome to the Deep Energy Podcast 1929 to 1932 - Chronosphere - Parts 1 - 4 Please remember to turn on automatic downloads, like and subscribe, tell a friend, share with your family and leave a review. All of those things help build the podcast. Thank you so much!! ………. This podcast is ad supported. We try the best we can to keep all of the ads at the front and the back of the podcast, but depending on the length of the podcast, there maybe ads in the middle. Please check my Bandcamp page for ad free podcasts. www.jimbutler.bandcamp.com ……………………….. Watch me play live on TikTok @jimbutlermusic or On the Insight Timer App as Jim Butler Links for all of the podcasts in the Deep Energy Podcast Network: Deep Energy Podcast (Current Episodes) https://podcasts.apple.com/us/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga/id511265415 https://open.spotify.com/show/1DhN56DzDKc0FhQqR23v9c Deep Energy Classics - All of the ORIGINAL Episodes  https://podcasts.apple.com/us/podcast/deep-energy-classics-original-episodes/id1734274408 https://www.spreaker.com/podcast/deep-energy-classics-original-episodes--6108618 https://open.spotify.com/show/7BjEFnqcyKWUkHcYdtFS25?si=05aeab39b5bc4a00 Deep Energy Daily Affirmations - Daily Affirmations to get you through the day https://podcasts.apple.com/us/podcast/deep-energy-daily-affirmations/id1729162791 https://open.spotify.com/show/0oaA8dRsWDQLkqeXmykGvu?si=461c7b47417b4e55 Deep Energy Guided Meditations - Guided Meditations to help through your day https://podcasts.apple.com/us/podcast/deep-energy-guided-meditations-with-michelle-davis-jim/id1732674561 https://open.spotify.com/show/1Kg2LTaFux10Ul94phybp8?si=ebbbf33757d64c13 https://www.spreaker.com/podcast/deep-energy-guided-meditations-with-michelle-davis-jim-butler--6098026 Slow Piano for Sleep - Solo Piano Pieces https://podcasts.apple.com/us/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and/id1626828397 https://www.spreaker.com/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and-relaxation--5572963 ………… www,jimbutlermusic.com jimbutlermusic@gmail.com All Social Media (FB - IG - YT - TT) is: @jimbutlermusic Merch: www.deepenergy.threadless.com Bandcamp Monthly No Ads Subscription/Patreon: www.jimbutler.bandcamp.com Custom Made Music: jimbutlermusic@gmail.com ………………….. Thank you for listening. All music is created, performed and composed by Jim Butler. AI IS NEVER USED TO CREATE MY MUSIC. Until the next time, please be kind to one another, peace, bye… …….. Original Image by the Dream App (not sponsored) or Canva (not sponsored) …………………. Become a supporter of this podcast: https://www.spreaker.com/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga-and-studying--4262945/support.

Background Music for Sleep, Meditation, Relaxation, Massage, Yoga, Studying and Therapy …… Hi everyone, this is Jim Butler and welcome to the Deep Energy Podcast 1929 to 1932 - Chronosphere - Parts 1 - 4 Please remember to turn on automatic downloads, like and subscribe, tell a friend, share with your family and leave a review. All of those things help build the podcast. Thank you so much!! ………. This podcast is ad supported. We try the best we can to keep all of the ads at the front and the back of the podcast, but depending on the length of the podcast, there maybe ads in the middle. Please check my Bandcamp page for ad free podcasts. www.jimbutler.bandcamp.com ……………………….. Watch me play live on TikTok @jimbutlermusic or On the Insight Timer App as Jim Butler Links for all of the podcasts in the Deep Energy Podcast Network: Deep Energy Podcast (Current Episodes) https://podcasts.apple.com/us/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga/id511265415 https://open.spotify.com/show/1DhN56DzDKc0FhQqR23v9c Deep Energy Classics - All of the ORIGINAL Episodes  https://podcasts.apple.com/us/podcast/deep-energy-classics-original-episodes/id1734274408 https://www.spreaker.com/podcast/deep-energy-classics-original-episodes--6108618 https://open.spotify.com/show/7BjEFnqcyKWUkHcYdtFS25?si=05aeab39b5bc4a00 Deep Energy Daily Affirmations - Daily Affirmations to get you through the day https://podcasts.apple.com/us/podcast/deep-energy-daily-affirmations/id1729162791 https://open.spotify.com/show/0oaA8dRsWDQLkqeXmykGvu?si=461c7b47417b4e55 Deep Energy Guided Meditations - Guided Meditations to help through your day https://podcasts.apple.com/us/podcast/deep-energy-guided-meditations-with-michelle-davis-jim/id1732674561 https://open.spotify.com/show/1Kg2LTaFux10Ul94phybp8?si=ebbbf33757d64c13 https://www.spreaker.com/podcast/deep-energy-guided-meditations-with-michelle-davis-jim-butler--6098026 Slow Piano for Sleep - Solo Piano Pieces https://podcasts.apple.com/us/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and/id1626828397 https://www.spreaker.com/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and-relaxation--5572963 ………… www,jimbutlermusic.com jimbutlermusic@gmail.com All Social Media (FB - IG - YT - TT) is: @jimbutlermusic Merch: www.deepenergy.threadless.com Bandcamp Monthly No Ads Subscription/Patreon: www.jimbutler.bandcamp.com Custom Made Music: jimbutlermusic@gmail.com ………………….. Thank you for listening. All music is created, performed and composed by Jim Butler. AI IS NEVER USED TO CREATE MY MUSIC. Until the next time, please be kind to one another, peace, bye… …….. Original Image by the Dream App (not sponsored) or Canva (not sponsored) …………………. Become a supporter of this podcast: https://www.spreaker.com/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga-and-studying--4262945/support.

Background Music for Sleep, Meditation, Relaxation, Massage, Yoga, Studying and Therapy …… Hi everyone, this is Jim Butler and welcome to the Deep Energy Podcast 1929 to 1932 - Chronosphere - Parts 1 - 4 Please remember to turn on automatic downloads, like and subscribe, tell a friend, share with your family and leave a review. All of those things help build the podcast. Thank you so much!! ………. This podcast is ad supported. We try the best we can to keep all of the ads at the front and the back of the podcast, but depending on the length of the podcast, there maybe ads in the middle. Please check my Bandcamp page for ad free podcasts. www.jimbutler.bandcamp.com ……………………….. Watch me play live on TikTok @jimbutlermusic or On the Insight Timer App as Jim Butler Links for all of the podcasts in the Deep Energy Podcast Network: Deep Energy Podcast (Current Episodes) https://podcasts.apple.com/us/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga/id511265415 https://open.spotify.com/show/1DhN56DzDKc0FhQqR23v9c Deep Energy Classics - All of the ORIGINAL Episodes  https://podcasts.apple.com/us/podcast/deep-energy-classics-original-episodes/id1734274408 https://www.spreaker.com/podcast/deep-energy-classics-original-episodes--6108618 https://open.spotify.com/show/7BjEFnqcyKWUkHcYdtFS25?si=05aeab39b5bc4a00 Deep Energy Daily Affirmations - Daily Affirmations to get you through the day https://podcasts.apple.com/us/podcast/deep-energy-daily-affirmations/id1729162791 https://open.spotify.com/show/0oaA8dRsWDQLkqeXmykGvu?si=461c7b47417b4e55 Deep Energy Guided Meditations - Guided Meditations to help through your day https://podcasts.apple.com/us/podcast/deep-energy-guided-meditations-with-michelle-davis-jim/id1732674561 https://open.spotify.com/show/1Kg2LTaFux10Ul94phybp8?si=ebbbf33757d64c13 https://www.spreaker.com/podcast/deep-energy-guided-meditations-with-michelle-davis-jim-butler--6098026 Slow Piano for Sleep - Solo Piano Pieces https://podcasts.apple.com/us/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and/id1626828397 https://www.spreaker.com/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and-relaxation--5572963 ………… www,jimbutlermusic.com jimbutlermusic@gmail.com All Social Media (FB - IG - YT - TT) is: @jimbutlermusic Merch: www.deepenergy.threadless.com Bandcamp Monthly No Ads Subscription/Patreon: www.jimbutler.bandcamp.com Custom Made Music: jimbutlermusic@gmail.com ………………….. Thank you for listening. All music is created, performed and composed by Jim Butler. AI IS NEVER USED TO CREATE MY MUSIC. Until the next time, please be kind to one another, peace, bye… …….. Original Image by the Dream App (not sponsored) or Canva (not sponsored) …………………. Become a supporter of this podcast: https://www.spreaker.com/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga-and-studying--4262945/support.

Background Music for Sleep, Meditation, Relaxation, Massage, Yoga, Studying and Therapy …… Hi everyone, this is Jim Butler and welcome to the Deep Energy Podcast 1929 to 1932 - Chronosphere - Parts 1 - 4 Please remember to turn on automatic downloads, like and subscribe, tell a friend, share with your family and leave a review. All of those things help build the podcast. Thank you so much!! ………. This podcast is ad supported. We try the best we can to keep all of the ads at the front and the back of the podcast, but depending on the length of the podcast, there maybe ads in the middle. Please check my Bandcamp page for ad free podcasts. www.jimbutler.bandcamp.com ……………………….. Watch me play live on TikTok @jimbutlermusic or On the Insight Timer App as Jim Butler Links for all of the podcasts in the Deep Energy Podcast Network: Deep Energy Podcast (Current Episodes) https://podcasts.apple.com/us/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga/id511265415 https://open.spotify.com/show/1DhN56DzDKc0FhQqR23v9c Deep Energy Classics - All of the ORIGINAL Episodes  https://podcasts.apple.com/us/podcast/deep-energy-classics-original-episodes/id1734274408 https://www.spreaker.com/podcast/deep-energy-classics-original-episodes--6108618 https://open.spotify.com/show/7BjEFnqcyKWUkHcYdtFS25?si=05aeab39b5bc4a00 Deep Energy Daily Affirmations - Daily Affirmations to get you through the day https://podcasts.apple.com/us/podcast/deep-energy-daily-affirmations/id1729162791 https://open.spotify.com/show/0oaA8dRsWDQLkqeXmykGvu?si=461c7b47417b4e55 Deep Energy Guided Meditations - Guided Meditations to help through your day https://podcasts.apple.com/us/podcast/deep-energy-guided-meditations-with-michelle-davis-jim/id1732674561 https://open.spotify.com/show/1Kg2LTaFux10Ul94phybp8?si=ebbbf33757d64c13 https://www.spreaker.com/podcast/deep-energy-guided-meditations-with-michelle-davis-jim-butler--6098026 Slow Piano for Sleep - Solo Piano Pieces https://podcasts.apple.com/us/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and/id1626828397 https://www.spreaker.com/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and-relaxation--5572963 ………… www,jimbutlermusic.com jimbutlermusic@gmail.com All Social Media (FB - IG - YT - TT) is: @jimbutlermusic Merch: www.deepenergy.threadless.com Bandcamp Monthly No Ads Subscription/Patreon: www.jimbutler.bandcamp.com Custom Made Music: jimbutlermusic@gmail.com ………………….. Thank you for listening. All music is created, performed and composed by Jim Butler. AI IS NEVER USED TO CREATE MY MUSIC. Until the next time, please be kind to one another, peace, bye… …….. Original Image by the Dream App (not sponsored) or Canva (not sponsored) …………………. Become a supporter of this podcast: https://www.spreaker.com/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga-and-studying--4262945/support.

Background Music for Sleep, Meditation, Relaxation, Massage, Yoga, Studying and Therapy …… Hi everyone, this is Jim Butler and welcome to the Deep Energy Podcast 1929 to 1932 - Chronosphere - Parts 1 - 4 Please remember to turn on automatic downloads, like and subscribe, tell a friend, share with your family and leave a review. All of those things help build the podcast. Thank you so much!! ………. This podcast is ad supported. We try the best we can to keep all of the ads at the front and the back of the podcast, but depending on the length of the podcast, there maybe ads in the middle. Please check my Bandcamp page for ad free podcasts. www.jimbutler.bandcamp.com ……………………….. Watch me play live on TikTok @jimbutlermusic or On the Insight Timer App as Jim Butler Links for all of the podcasts in the Deep Energy Podcast Network: Deep Energy Podcast (Current Episodes) https://podcasts.apple.com/us/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga/id511265415 https://open.spotify.com/show/1DhN56DzDKc0FhQqR23v9c Deep Energy Classics - All of the ORIGINAL Episodes  https://podcasts.apple.com/us/podcast/deep-energy-classics-original-episodes/id1734274408 https://www.spreaker.com/podcast/deep-energy-classics-original-episodes--6108618 https://open.spotify.com/show/7BjEFnqcyKWUkHcYdtFS25?si=05aeab39b5bc4a00 Deep Energy Daily Affirmations - Daily Affirmations to get you through the day https://podcasts.apple.com/us/podcast/deep-energy-daily-affirmations/id1729162791 https://open.spotify.com/show/0oaA8dRsWDQLkqeXmykGvu?si=461c7b47417b4e55 Deep Energy Guided Meditations - Guided Meditations to help through your day https://podcasts.apple.com/us/podcast/deep-energy-guided-meditations-with-michelle-davis-jim/id1732674561 https://open.spotify.com/show/1Kg2LTaFux10Ul94phybp8?si=ebbbf33757d64c13 https://www.spreaker.com/podcast/deep-energy-guided-meditations-with-michelle-davis-jim-butler--6098026 Slow Piano for Sleep - Solo Piano Pieces https://podcasts.apple.com/us/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and/id1626828397 https://www.spreaker.com/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and-relaxation--5572963 ………… www,jimbutlermusic.com jimbutlermusic@gmail.com All Social Media (FB - IG - YT - TT) is: @jimbutlermusic Merch: www.deepenergy.threadless.com Bandcamp Monthly No Ads Subscription/Patreon: www.jimbutler.bandcamp.com Custom Made Music: jimbutlermusic@gmail.com ………………….. Thank you for listening. All music is created, performed and composed by Jim Butler. AI IS NEVER USED TO CREATE MY MUSIC. Until the next time, please be kind to one another, peace, bye… …….. Original Image by the Dream App (not sponsored) or Canva (not sponsored) …………………. Become a supporter of this podcast: https://www.spreaker.com/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga-and-studying--4262945/support.

Background Music for Sleep, Meditation, Relaxation, Massage, Yoga, Studying and Therapy …… Hi everyone, this is Jim Butler and welcome to the Deep Energy Podcast 1929 to 1932 - Chronosphere - Parts 1 - 4 Please remember to turn on automatic downloads, like and subscribe, tell a friend, share with your family and leave a review. All of those things help build the podcast. Thank you so much!! ………. This podcast is ad supported. We try the best we can to keep all of the ads at the front and the back of the podcast, but depending on the length of the podcast, there maybe ads in the middle. Please check my Bandcamp page for ad free podcasts. www.jimbutler.bandcamp.com ……………………….. Watch me play live on TikTok @jimbutlermusic or On the Insight Timer App as Jim Butler Links for all of the podcasts in the Deep Energy Podcast Network: Deep Energy Podcast (Current Episodes) https://podcasts.apple.com/us/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga/id511265415 https://open.spotify.com/show/1DhN56DzDKc0FhQqR23v9c Deep Energy Classics - All of the ORIGINAL Episodes  https://podcasts.apple.com/us/podcast/deep-energy-classics-original-episodes/id1734274408 https://www.spreaker.com/podcast/deep-energy-classics-original-episodes--6108618 https://open.spotify.com/show/7BjEFnqcyKWUkHcYdtFS25?si=05aeab39b5bc4a00 Deep Energy Daily Affirmations - Daily Affirmations to get you through the day https://podcasts.apple.com/us/podcast/deep-energy-daily-affirmations/id1729162791 https://open.spotify.com/show/0oaA8dRsWDQLkqeXmykGvu?si=461c7b47417b4e55 Deep Energy Guided Meditations - Guided Meditations to help through your day https://podcasts.apple.com/us/podcast/deep-energy-guided-meditations-with-michelle-davis-jim/id1732674561 https://open.spotify.com/show/1Kg2LTaFux10Ul94phybp8?si=ebbbf33757d64c13 https://www.spreaker.com/podcast/deep-energy-guided-meditations-with-michelle-davis-jim-butler--6098026 Slow Piano for Sleep - Solo Piano Pieces https://podcasts.apple.com/us/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and/id1626828397 https://www.spreaker.com/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and-relaxation--5572963 ………… www,jimbutlermusic.com jimbutlermusic@gmail.com All Social Media (FB - IG - YT - TT) is: @jimbutlermusic Merch: www.deepenergy.threadless.com Bandcamp Monthly No Ads Subscription/Patreon: www.jimbutler.bandcamp.com Custom Made Music: jimbutlermusic@gmail.com ………………….. Thank you for listening. All music is created, performed and composed by Jim Butler. AI IS NEVER USED TO CREATE MY MUSIC. Until the next time, please be kind to one another, peace, bye… …….. Original Image by the Dream App (not sponsored) or Canva (not sponsored) …………………. Become a supporter of this podcast: https://www.spreaker.com/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga-and-studying--4262945/support.

Background Music for Sleep, Meditation, Relaxation, Massage, Yoga, Studying and Therapy …… Hi everyone, this is Jim Butler and welcome to the Deep Energy Podcast 1929 to 1932 - Chronosphere - Parts 1 - 4 Please remember to turn on automatic downloads, like and subscribe, tell a friend, share with your family and leave a review. All of those things help build the podcast. Thank you so much!! ………. This podcast is ad supported. We try the best we can to keep all of the ads at the front and the back of the podcast, but depending on the length of the podcast, there maybe ads in the middle. Please check my Bandcamp page for ad free podcasts. www.jimbutler.bandcamp.com ……………………….. Watch me play live on TikTok @jimbutlermusic or On the Insight Timer App as Jim Butler Links for all of the podcasts in the Deep Energy Podcast Network: Deep Energy Podcast (Current Episodes) https://podcasts.apple.com/us/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga/id511265415 https://open.spotify.com/show/1DhN56DzDKc0FhQqR23v9c Deep Energy Classics - All of the ORIGINAL Episodes  https://podcasts.apple.com/us/podcast/deep-energy-classics-original-episodes/id1734274408 https://www.spreaker.com/podcast/deep-energy-classics-original-episodes--6108618 https://open.spotify.com/show/7BjEFnqcyKWUkHcYdtFS25?si=05aeab39b5bc4a00 Deep Energy Daily Affirmations - Daily Affirmations to get you through the day https://podcasts.apple.com/us/podcast/deep-energy-daily-affirmations/id1729162791 https://open.spotify.com/show/0oaA8dRsWDQLkqeXmykGvu?si=461c7b47417b4e55 Deep Energy Guided Meditations - Guided Meditations to help through your day https://podcasts.apple.com/us/podcast/deep-energy-guided-meditations-with-michelle-davis-jim/id1732674561 https://open.spotify.com/show/1Kg2LTaFux10Ul94phybp8?si=ebbbf33757d64c13 https://www.spreaker.com/podcast/deep-energy-guided-meditations-with-michelle-davis-jim-butler--6098026 Slow Piano for Sleep - Solo Piano Pieces https://podcasts.apple.com/us/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and/id1626828397 https://www.spreaker.com/podcast/slow-piano-for-sleep-music-for-sleep-meditation-and-relaxation--5572963 ………… www,jimbutlermusic.com jimbutlermusic@gmail.com All Social Media (FB - IG - YT - TT) is: @jimbutlermusic Merch: www.deepenergy.threadless.com Bandcamp Monthly No Ads Subscription/Patreon: www.jimbutler.bandcamp.com Custom Made Music: jimbutlermusic@gmail.com ………………….. Thank you for listening. All music is created, performed and composed by Jim Butler. AI IS NEVER USED TO CREATE MY MUSIC. Until the next time, please be kind to one another, peace, bye… …….. Original Image by the Dream App (not sponsored) or Canva (not sponsored) …………………. Become a supporter of this podcast: https://www.spreaker.com/podcast/deep-energy-podcast-music-for-sleep-meditation-yoga-and-studying--4262945/support.

This special episode recorded live at KubeCon Salt Lake City last November is with Martin Mao, CEO and co-founder at Chronosphere.We talked about how M3 was foundational to the early history of Chronosphere, and how the ability to leverage M3, which Martin and his co-founder had written while they were still working at Uber. One of the most important aspects of this story is that since M3 is the foundation Chronosphere is built on, the fact that it was developed over four years at Uber while they were still on Uber's payroll meant that when they decided to build a company it allowed them to get to market dramatically faster than would have been possible otherwise. Chronosphere's core platform is a proprietary SaaS product, but still has a significant relationship with two other projects: Perses, which was developed at Chronosphere and donated to the CNCF in 2024; and FluentBit, a CNCF graduated project that was originally developed by Calyptia and became part of Chronosphere when it acquired Calyptia. We talked about: The pros and cons of donating projects to the CNCF, from both the perspectives of the company creating the project and the interests of the community and project itselfWhy Chronosphere's core platform isn't open source itselfHow a company can end up getting financial advantages from being the stewards of large open source community, even if the connection doesn't always seem obviousHow product roadmaps are managed for the two projects versus how it's managed for Chronosphere's proprietary products. If you're building a company around an open source project and aren't sure how to manage the relationship between the project and product, you might want to work with me or come to Open Source Founders Summit this May. 

Segments Early Adopters News Freebies Backlog Blog White Elephant One Last Thing Don't forget to follow/reach us at: Twitter: @SuperGGRadio Email: SuperGGRadio@gmail.com Wordpress: www.superggradio.wordpress.com Facebook: https://www.facebook.com/SuperGGRadio Twitch: Twitch.tv/superggradio Youtube: http://tiny.cc/1xr07y Games Discussed: One Bear Army https://store.steampowered.com/app/2646480/One_Bear_Army/ Enter the Chronosphere https://store.steampowered.com/app/1969810/Enter_the_Chronosphere/ Driving is Hard https://store.steampowered.com/app/3175860/Driving_Is_Hard/ Dragon Age Veilguard Interaction Isn't Explicit Music Credits: Introduction: I Got A Story by DJ Quads Intermission:Chill Jazzy Lofi Hip Hop by DJ Quads End Credits: Show Me by DJ Quads Mixed by Joel DeWitte Edited by Joel DeWitte

Jeff and Christian welcome Lucy James from Gamespot and Giant Bomb to the show this week to discuss a new report that claims gamers spend more time watching others playing than playing themselves, Apple's plan to support PSVR 2 motion controllers on Vision Pro, and the huge PC Gamer Most Wanted showcase. The Playlist: Lucy: Indiana Jones and the Great Circle, After Inc Christian: Indiana Jones and the Great Circle Jeff: Path of Exile 2 VR Talk: Christian: Skydance's Behemoth Jeff: Skydance's Behemoth Parting Gifts!

Chronosphere Fiction is a story telling podcast where writers' creations come to life with sound effects and music. Our Narrator sets the scenes from a big empty theater. An earthquake in a British tourist cave exposes the skeleton of a murder victim. However, a forensics examination reveals further details so shocking that baffled police must close off the investigation to the public and hastily summon leading scientists. Learn more about your ad choices. Visit megaphone.fm/adchoices

Chronosphere Fiction is a story telling podcast where writers' creations come to life with sound effects and music. Our Narrator sets the scenes from a big empty theater. An earthquake in a British tourist cave exposes the skeleton of a murder victim. However, a forensics examination reveals further details so shocking that baffled police must close off the investigation to the public and hastily summon leading scientists. Learn more about your ad choices. Visit megaphone.fm/adchoices

From elementary school music teacher to a Senior Cloud Engineer at Defiance Digital, Mike Gray has lived quite a few lives. He hit it off with Corey during the AWS New York Summit this past summer. What brought them together? Their mutual frustration at what dominated the discourse of the event: the current fascination with GenAI. Although Mike has his qualms with AI, he also enjoys working with it quite a bit. As a matter of fact, he uses it to help automate his home and appliances! From exploring what goes into consulting customers on cloud products, to the nightmare of having your kids hijacking your Alexa with an endless stream of children's music, this episode features twists and turns, leaving no stone unturned.Show Highlights:(0:00) Intro(0:40) Chronosphere sponsor read(1:14) The responsibilities of a Senior Cloud Engineer at Defiance Digital(2:07) Cloud product consulting(3:27) The challenges of working with Kubernetes(7:50) Mike's problems with AI(9:33) Challenges with home automation(15:38) Chronosphere sponsor read(16:13) The joys of home automation(18:34) Prefered hardware for home automation(20:10) Home automation and the impact on your relationships and kids(23:43) Going from teaching kids to the world of tech(28:42) Where you can find more from MikeAbout Mike GrayMike Gray is a technologist, currently employed as a Senior Cloud Engineer, with a focus on Amazon Web Services and Google Cloud Platform.In previous roles, he has worked with companies of every size, from single-digit employee startups to Fortune 500 companies. In a past life, Mike has worked as a professional musician and music educator.Mike is also an active open source contributor, splitting time between OpenVoiceOS and Neon AI. Think of it as open source Alexa, but all your data stays at home.LinksMike's website: https://graywind.orgMike's email: mike@graywind.orgMike's Twitter: https://x.com/saxmanmikeSponsorChronosphere: https://chronosphere.io/?utm_source=duckbill-group&utm_medium=podcast

It turns out, you don't need to step outside to observe the clouds. On this episode, we're joined by Chronosphere Field CTO Ian Smith. He and Corey delve into the innovative solutions Chronosphere offers, share insights from Ian's experience in the industry, and discuss the future of cloud-native technologies. Whether you're a seasoned cloud professional or new to the field, this conversation with Ian Smith is packed with valuable perspectives and actionable takeaways.Show Highlights:(0:00) Intro(0:42) Chronosphere sponsor read(1:53) The role of Chief of Staff at Chronosphere(2:45) Getting recognized in the Gartner Magic Quadrant(4:42) Talking about the buying process(8:26) The importance of observability(10:18) Guiding customers as a vendor(12:19)  Chronosphere sponsor read(12:46) What should you do as an observability buyer(16:01) Helping orgs understand observability(19:56) Avoiding toxicly positive endorsements(24:15) Being transparent as a vendor(27:43) The myth of "winner take all"(30:02) Short term fixes vs. long term solutions(33:54) Where you can find more from Ian and ChronosphereAbout Ian SmithIan Smith is Field CTO at Chronosphere where he works across sales, marketing, engineering and product to deliver better insights and outcomes to observability teams supporting high-scale cloud-native environments. Previously, he worked with observability teams across the software industry in pre-sales roles at New Relic, Wavefront, PagerDuty and Lightstep.LinksChronosphere: https://chronosphere.io/?utm_source=duckbill-group&utm_medium=podcastIan's Twitter: https://x.com/datasmithingIan's LinkedIn: https://www.linkedin.com/in/ismith314159/SponsorChronosphere: https://chronosphere.io/?utm_source=duckbill-group&utm_medium=podcast

After years of trying, Corey has finally convinced a TAM to come on the show! In this lively episode, AWS Senior Technical Account Manager Shlomo Dubrowin takes the mic to share his fascinating experiences dealing with cloud complexities. Listen in as Shlomo recounts building AWS Reasonable Account Defaults from scratch, stresses the importance of writing a solid application, and shares the benefits of leveraging GenAI to help maintain his work. Don't miss this entertaining and insightful conversation that could save you a few bucks!Show Highlights:(0:00) Intro(0:42) Chronosphere sponsor read(1:15) Finally getting a TAM on the show(2:24) Providing quality customer service as a TAM(5:31) AWS Reasonable Account Defaults(11:01) What went into crafting AWS Reasonable Accounts Defaults(12:20) Chronosphere sponsor read(12:54) Writing a program that won't break easily(17:25) Optimizing billing data(19:53) Transparency in costs(21:27) Expanding AWS Reasonable Account Defaults(23:34) Further optimizing AWS Reasonable Account Defaults in the future(26:18) Building with GenAI(29:01) Where you can find more from ShlomoAbout Shlomo DubrowinShlomo Dubrowin has been a TAM for over 6 years supporting AWS customers from startups through to Fortune 100 companies. He has spoken at re:Invent twice and has specialized in Cost Optimization. Shlomo has been in the tech industry since 1994. And he lives with his wife, son and 2 dogs.LinksClouded Torah: https://www.clouded-torah.org/SponsorChronosphere: https://chronosphere.io/?utm_source=duckbill-group&utm_medium=podcast 

In this Screaming in the Cloud Replay, we revisit a spirited debated between Corey and the VP of Product and Industry Marketing at Google Cloud, Brian Hall.  The topic — How much time should one spend in a job? But thankfully, their conversation doesn't limit itself to just that! Corey and Brian chat about how social media's failure to capture nuance and context can lead to some unfortunate misinterpretations. Brian offers some insight on his significant amount of time spent at Microsoft under various roles. He gives his perspective on how one should optimize their career path for where they want to go, and not just follow the money. Tune in to see how Corey and Brian let the dust settle, and develop what was a disagreement into a well-rounded conversation.Show Highlights:(0:00) Intro(1:02) Chronosphere sponsor read(1:36) Job hopping vs. job loyalty(6:14) Being in the right place at the right time(9:57) Investing in the job vs. the job investing in you(13:31) Weighing the cost of job hopping(20:14) Chronosphere sponsor read(20:47) Changing jobs to get a raise(24:02) How to attract people as a cloud employer(26:31) Changing paths into the industry(30:14) What's ahead for Brian(32:33) Where you can find more from BrianAbout Brian HallBrian Hall leads the Google Cloud Product and Industry Marketing team - focused on accelerating the growth of Google Cloud. Before joining Google, he spent more than 25 years in different forms of product marketing or engineering.Brian is the father of three children who are all named after trees in different ways. He met his wife Edie at the beginning of their first year at Yale University, where he studied math, econ, and philosophy and was the captain of the Swim and Dive team my senior year. Edie has a PhD in forestry and runs a sustainability and forestry consulting firm she started, that is aptly named “Three Trees Consulting”. They love the outdoors, tennis, running, and adventures in Brian's 1986 Volkswagen Van, which is his first and only car, that he can't bring myself to get rid of.Links:Twitter: https://twitter.com/IsForAtLinkedIn: https://www.linkedin.com/in/brhall/Episode 10: https://www.lastweekinaws.com/podcast/screaming-in-the-cloud/episode-10-education-is-not-ready-for-teacherless/Original Episode:https://www.lastweekinaws.com/podcast/screaming-in-the-cloud/letting-the-dust-settle-on-job-hopping-with-brian-hall/Sponsorhttps://chronosphere.io/?utm_source=duckbill-group&utm_medium=podcast

Much of the discourse surrounding GenAI has centered on replacement, but what if tools focused on harmony instead? In this episode of Screaming in the Cloud, Kubiya CEO Amit Eyal Govrin explains why his company is flipping the script on AI. Amit and Corey discuss the perks and shortcomings of today's automation, how Kubiya functions as a teammate alongside its human counterparts, and the GenAI trends that aren't getting the attention they deserve. If you're worrying about your job security in the current AI climate, this discussion may help put your fears at ease.Show Highlights:(0:00) Intro(0:47) Chronosphere sponsor read(1:21) What Amit and Kubiya are building(5:34) Pros and cons of automation(9:10) Building a virtual teammate(12:39) Implementing AI with nuance(16:16) Real world applications of the tech(18:09) Firefly ad read(18:43) The value of human review in the world of AI(21:10) Complexities (or lack thereof) of GenAI(24:36) What people are sleeping on when it comes to GenAI(28:08) Where you can learn more about KubiyaAbout Amit Eyal Govrin:Amit is the CEO of Kubiya, helping the industry Break through the Time-To-Automation Paradox. As an early pioneer in the FinOps domain - executive position at Cloudyn (currently Azure Cost Manager), Zesty (advisor, early investor) and leading DevOps partnerships at AWS.Links Referenced:Kubiya: kubiya.aiSponsorChronosphere: https://chronosphere.io/?utm_source=duckbill-group&utm_medium=podcast

On this episode of DevOps Dialogues: Insights & Innovations, I am joined by Chronosphere's CEO, Martin Mao, for discussion of the partnership with CrowdStrike and the recent acquisition of Calyptia. Our discussion covers: Chronosphere recently unveiled “Logs powered by CrowdStrike,” a comprehensive log storage and visualization solution, and how embedding CrowdStrike Falcon LogScale within Chronosphere's cloud-native observability platform helps clients Chronosphere's recently acquisition of Calyptia, founded by the original creators of the Fluent Ecosystem What's next for Chronosphere, and the next sets of advancements in the observability and security space Cloud native coming off Kubecon These topics reflect ongoing discussions, challenges, and innovations within the DevOps community.  

The Pass The Controller Podcast is a show where a couple of best friends dive into the latest in gaming and nerd culture. In this episode, Brenden, Mike, Todd, and Dom sit down and chat about what they've been playing, Dragon Quest 1 (Dragon Warrior), Princess Peach Showtime!, FFXIV, Brenden had the chance to preview Visions of Mana, and the gang recaps their favorite PAX East 2024 games and moments. Some highlights include: LUCID, Enter the Chronosphere, and Fretless! Please get vaccinated. Be sure to SUBSCRIBE and LEAVE A REVIEW on Apple Podcasts, Spotify, or wherever you listen to the show! passthecontroller.io​​ twitter.com/passcontroller​​

This is the PAX East 2024 retrospective and run-through of all of the games I played! Woooo! Games featured: Animal Well (https://store.steampowered.com/app/813230/ANIMAL_WELL/): The Art of Flight (https://store.steampowered.com/app/1706800/The_Art_Of_Flight/) Duck Paradox (https://store.steampowered.com/app/2058150/Duck_Paradox/) Enter the Chronosphere (https://store.steampowered.com/app/1969810/Enter_the_Chronosphere/) Fallen Aces (https://store.steampowered.com/app/1411910/Fallen_Aces/) Fretless (https://store.steampowered.com/app/2429050/Fretless__The_Wrath_of_Riffson/) Lucid (https://store.steampowered.com/app/1717730/LUCID/) So to Speak (https://store.steampowered.com/app/1779030/So_to_Speak/) Sorry, We're Closed (https://store.steampowered.com/app/1796580/Sorry_Were_Closed/) Tape to Tape (https://store.steampowered.com/app/1566200/Tape_to_Tape/) Throne of Bone (https://store.steampowered.com/app/1866630/Throne_of_Bone/) YouTube VoD of the Nintendo DS panel I participated in! (https://youtu.be/exJGKqBZ9T4?si=1YzUCp0FvvuHz6Fc) Support Tales from the Backlog on Patreon! (https://patreon.com/realdavejackson) or buy me a coffee on Ko-fi (https://ko-fi.com/realdavejackson)! Join the Tales from the Backlog Discord server! (https://discord.gg/V3ZHz3vYQR) Social Media: Instagram (https://www.instagram.com/talesfromthebacklog/) Twitter (https://twitter.com/tftblpod) Facebook (https://www.facebook.com/TalesfromtheBacklog/) Cover art by Jack Allen- find him at https://www.instagram.com/jackallencaricatures/ and his other pages (https://linktr.ee/JackAllenCaricatures) Music composed by Bert Cole- find more music at bitbybitsound.com (www.bitbybitsound.com) Patreon: patreon.com/bitbybitsound Twitter: @BitByBitSound Listen to A Top 3 Podcast on Apple (https://podcasts.apple.com/us/podcast/a-top-3-podcast/id1555269504), Spotify (https://open.spotify.com/show/2euGp3pWi7Hy1c6fmY526O?si=0ebcb770618c460c) and other podcast platforms (atop3podcast.fireside.fm)!

Rachel Dines, Head of Product and Technical Marketing at Chronosphere, joins Corey on Screaming in the Cloud to discuss why creating a cloud-native observability strategy is so critical, and the challenges that come with both defining and accomplishing that strategy to fit your current and future observability needs. Rachel explains how Chronosphere is taking an open-source approach to observability, and why it's more important than ever to acknowledge that the stakes and costs are much higher when it comes to observability in the cloud. About RachelRachel leads product and technical marketing for Chronosphere. Previously, Rachel wore lots of marketing hats at CloudHealth (acquired by VMware), and before that, she led product marketing for cloud-integrated storage at NetApp. She also spent many years as an analyst at Forrester Research. Outside of work, Rachel tries to keep up with her young son and hyper-active dog, and when she has time, enjoys crafting and eating out at local restaurants in Boston where she's based.Links Referenced: Chronosphere: https://chronosphere.io/ LinkedIn: https://www.linkedin.com/in/rdines/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Today's featured guest episode is brought to us by our friends at Chronosphere, and they have also brought us Rachel Dines, their Head of Product and Solutions Marketing. Rachel, great to talk to you again.Rachel: Hi, Corey. Yeah, great to talk to you, too.Corey: Watching your trajectory has been really interesting, just because starting off, when we first started, I guess, learning who each other were, you were working at CloudHealth which has since become VMware. And I was trying to figure out, huh, the cloud runs on money. How about that? It feels like it was a thousand years ago, but neither one of us is quite that old.Rachel: It does feel like several lifetimes ago. You were just this snarky guy with a few followers on Twitter, and I was trying to figure out what you were doing mucking around with my customers [laugh]. Then [laugh] we kind of both figured out what we're doing, right?Corey: So, speaking of that iterative process, today, you are at Chronosphere, which is an observability company. We would have called it a monitoring company five years ago, but now that's become an insult after the observability war dust has settled. So, I want to talk to you about something that I've been kicking around for a while because I feel like there's a gap somewhere. Let's say that I build a crappy web app—because all of my web apps inherently are crappy—and it makes money through some mystical form of alchemy. And I have a bunch of users, and I eventually realize, huh, I should probably have a better observability story than waiting for the phone to ring and a customer telling me it's broken.So, I start instrumenting various aspects of it that seem to make sense. Maybe I go too low level, like looking at all the discs on every server to tell me if they're getting full or not, like their ancient servers. Maybe I just have a Pingdom equivalent of is the website up enough to respond to a packet? And as I wind up experiencing different failure modes and getting yelled at by different constituencies—in my own career trajectory, my own boss—you start instrumenting for all those different kinds of breakages, you start aggregating the logs somewhere and the volume gets bigger and bigger with time. But it feels like it's sort of a reactive process as you stumble through that entire environment.And I know it's not just me because I've seen this unfold in similar ways in a bunch of different companies. It feels to me, very strongly, like it is something that happens to you, rather than something you set about from day one with a strategy in mind. What's your take on an effective way to think about strategy when it comes to observability?Rachel: You just nailed it. That's exactly the kind of progression that we so often see. And that's what I really was excited to talk with you about today—Corey: Oh, thank God. I was worried for a minute there that you'd be like, “What the hell are you talking about? Are you just, like, some sort of crap engineer?” And, “Yes, but it's mean of you to say it.” But yeah, what I'm trying to figure out is there some magic that I just was never connecting? Because it always feels like you're in trouble because the site's always broken, and oh, like, if the disk fills up, yeah, oh, now we're going to start monitoring to make sure the disk doesn't fill up. Then you wind up getting barraged with alerts, and no one wins, and it's an uncomfortable period of time.Rachel: Uncomfortable period of time. That is one very polite way to put it. I mean, I will say, it is very rare to find a company that actually sits down and thinks, “This is our observability strategy. This is what we want to get out of observability.” Like, you can think about a strategy and, like, the old school sense, and you know, as an industry analyst, so I'm going to have to go back to, like, my roots at Forrester with thinking about, like, the people, and the process, and the technology.But really what the bigger component here is like, what's the business impact? What do you want to get out of your observability platform? What are you trying to achieve? And a lot of the time, people have thought, “Oh, observability strategy. Great, I'm just going to buy a tool. That's it. Like, that's my strategy.”And I hate to bring it to you, but buying tools is not a strategy. I'm not going to say, like, buy this tool. I'm not even going to say, “Buy Chronosphere.” That's not a strategy. Well, you should buy Chronosphere. But that's not a strategy.Corey: Of course. I'm going to throw the money by the wheelbarrow at various observability vendors, and hope it solves my problem. But if that solved the problem—I've got to be direct—I've never spoken to those customers.Rachel: Exactly. I mean, that's why this space is such a great one to come in and be very disruptive in. And I think, back in the days when we were running in data centers, maybe even before virtual machines, you could probably get away with not having a monitoring strategy—I'm not going to call it observability; it's not we call the back then—you could get away with not having a strategy because what was the worst that was going to happen, right? It wasn't like there was a finite amount that your monitoring bill could be, there was a finite amount that your customer impact could be. Like, you're paying the penny slots, right?We're not on the penny slots anymore. We're in the $50 craps table, and it's Las Vegas, and if you lose the game, you're going to have to run down the street without your shirt. Like, the game and the stakes have changed, and we're still pretending like we're playing penny slots, and we're not anymore.Corey: That's a good way of framing it. I mean, I still remember some of my biggest observability challenges were building highly available rsyslog clusters so that you could bounce a member and not lose any log data because some of that was transactionally important. And we've gone beyond that to a stupendous degree, but it still feels like you don't wind up building this into the application from day one. More's the pity because if you did, and did that intelligently, that opens up a whole world of possibilities. I dream of that changing where one day, whenever you start to build an app, oh, and we just push the button and automatically instrument with OTel, so you instrument the thing once everywhere it makes sense to do it, and then you can do your vendor selection and what you said were decisions later in time. But these days, we're not there.Rachel: Well, I mean, and there's also the question of just the legacy environment and the tech debt. Even if you wanted to, the—actually I was having a beer yesterday with a friend who's a VP of Engineering, and he's got his new environment that they're building with observability instrumented from the start. How beautiful. They've got OTel, they're going to have tracing. And then he's got his legacy environment, which is a hot mess.So, you know, there's always going to be this bridge of the old and the new. But this was where it comes back to no matter where you're at, you can stop and think, like, “What are we doing and why?” What is the cost of this? And not just cost in dollars, which I know you and I could talk about very deeply for a long period of time, but like, the opportunity costs. Developers are working on stuff that they could be working on something that's more valuable.Or like the cost of making people work round the clock, trying to troubleshoot issues when there could be an easier way. So, I think it's like stepping back and thinking about cost in terms of dollar sense, time, opportunity, and then also impact, and starting to make some decisions about what you're going to do in the future that's different. Once again, you might be stuck with some legacy stuff that you can't really change that much, but [laugh] you got to be realistic about where you're at.Corey: I think that that is a… it's a hard lesson to be very direct, in that, companies need to learn it the hard way, for better or worse. Honestly, this is one of the things that I always noticed in startup land, where you had a whole bunch of, frankly, relatively early-career engineers in their early-20s, if not younger. But then the ops person was always significantly older because the thing you actually want to hear from your ops person, regardless of how you slice it, is, “Oh, yeah, I've seen this kind of problem before. Here's how we fixed it.” Or even better, “Here's the thing we're doing, and I know how that's going to become a problem. Let's fix it before it does.” It's the, “What are you buying by bringing that person in?” “Experience, mostly.”Rachel: Yeah, that's an interesting point you make, and it kind of leads me down this little bit of a side note, but a really interesting antipattern that I've been seeing in a lot of companies is that more seasoned ops person, they're the one who everyone calls when something goes wrong. Like, they're the one who, like, “Oh, my God, I don't know how to fix it. This is a big hairy problem,” I call that one ops person, or I call that very experienced person. That experience person then becomes this huge bottleneck into solving problems that people don't really—they might even be the only one who knows how to use the observability tool. So, if we can't find a way to democratize our observability tooling a little bit more so, like, just day-to-day engineers, like, more junior engineers, newer ones, people who are still ramping, can actually use the tool and be successful, we're going to have a big problem when these ops people walk out the door, maybe they retire, maybe they just get sick of it. We have these massive bottlenecks in organizations, whether it's ops or DevOps or whatever, that I see often exacerbated by observability tools. Just a side note.Corey: Yeah. On some level, it feels like a lot of these things can be fixed with tooling. And I'm not going to say that tools aren't important. You ever tried to implement observability by hand? It doesn't work. There have to be computers somewhere in the loop, if nothing else.And then it just seems to devolve into a giant swamp of different companies, doing different things, taking different approaches. And, on some level, whenever you read the marketing or hear the stories any of these companies tell you also to normalize it from translating from whatever marketing language they've got into something that comports with the reality of your own environment and seeing if they align. And that feels like it is so much easier said than done.Rachel: This is a noisy space, that is for sure. And you know, I think we could go out to ten people right now and ask those ten people to define observability, and we would come back with ten different definitions. And then if you throw a marketing person in the mix, right—guilty as charged, and I know you're a marketing person, too, Corey, so you got to take some of the blame—it gets mucky, right? But like I said a minute ago, the answer is not tools. Tools can be part of the strategy, but if you're just thinking, “I'm going to buy a tool and that's going to solve my problem,” you're going to end up like this company I was talking to recently that has 25 different observability tools.And not only do they have 25 different observability tools, what's worse is they have 25 different definitions for their SLOs and 25 different names for the same metric. And to be honest, it's just a mess. I'm not saying, like, go be Draconian and, you know, tell all the engineers, like, “You can only use this tool [unintelligible 00:10:34] use that tool,” you got to figure out this kind of balance of, like, hands-on, hands-off, you know? How much do you centralize, how much do you push and standardize? Otherwise, you end up with just a huge mess.Corey: On some level, it feels like it was easier back in the days of building it yourself with Nagios because there's only one answer, and it sucks, unless you want to start going down the world of HP OpenView. Which step one: hire a 50-person team to manage OpenView. Okay, that's not going to solve my problem either. So, let's get a little more specific. How does Chronosphere approach this?Because historically, when I've spoken to folks at Chronosphere, there isn't that much of a day one story, in that, “I'm going to build a crappy web app. Let's instrument it for Chronosphere.” There's a certain, “You must be at least this tall to ride,” implicit expectation built into the product just based upon its origins. And I'm not saying that doesn't make sense, but it also means there's really no such thing as a greenfield build out for you either.Rachel: Well, yes and no. I mean, I think there's no green fields out there because everyone's doing something for observability, or monitoring, or whatever you want to call it, right? Whether they've got Nagios, whether they've got the Dog, whether they've got something else in there, they have some way of introspecting their systems, right? So, one of the things that Chronosphere is built on, that I actually think this is part of something—a way you might think about building out an observability strategy as well, is this concept of control and open-source compatibility. So, we only can collect data via open-source standards. You have to send this data via Prometheus, via Open Telemetry, it could be older standards, like, you know, statsd, Graphite, but we don't have any proprietary instrumentation.And if I was making a recommendation to somebody building out their observability strategy right now, I would say open, open, open, all day long because that gives you a huge amount of flexibility in the future. Because guess what? You know, you might put together an observability strategy that seems like it makes sense for right now—actually, I was talking to a B2B SaaS company that told me that they made a choice a couple of years ago on an observability tool. It seemed like the right choice at the time. They were growing so fast, they very quickly realized it was a terrible choice.But now, it's going to be really hard for them to migrate because it's all based on proprietary standards. Now, of course, a few years ago, they didn't have the luxury of Open Telemetry and all of these, but now that we have this, we can use these to kind of future-proof our mistakes. So, that's one big area that, once again, both my recommendation and happens to be our approach at Chronosphere.Corey: I think that that's a fair way of viewing it. It's a constant challenge, too, just because increasingly—you mentioned the Dog earlier, for example—I will say that for years, I have been asked whether or not at The Duckbill Group, we look at Azure bills or GCP bills. Nope, we are pure AWS. Recently, we started to hear that same inquiry specifically around Datadog, to the point where it has become a board-level concern at very large companies. And that is a challenge, on some level.I don't deviate from my typical path of I fix AWS bills, and that's enough impossible problems for one lifetime, but there is a strong sense of you want to record as much as possible for a variety of excellent reasons, but there's an implicit cost to doing that, and in many cases, the cost of observability becomes a massive contributor to the overall cost. Netflix has said in talks before that they're effectively an observability company that also happens to stream movies, just because it takes so much effort, engineering, and raw computing resources in order to get that data do something actionable with it. It's a hard problem.Rachel: It's a huge problem, and it's a big part of why I work at Chronosphere, to be honest. Because when I was—you know, towards the tail end at my previous company in cloud cost management, I had a lot of customers coming to me saying, “Hey, when are you going to tackle our Dog or our New Relic or whatever?” Similar to the experience you're having now, Corey, this was happening to me three, four years ago. And I noticed that there is definitely a correlation between people who are having these really big challenges with their observability bills and people that were adopting, like Kubernetes, and microservices and cloud-native. And it was around that time that I met the Chronosphere team, which is exactly what we do, right? We focus on observability for these cloud-native environments where observability data just goes, like, wild.We see 10X 20X as much observability data and that's what's driving up these costs. And yeah, it is becoming a board-level concern. I mean, and coming back to the concept of strategy, like if observability is the second or third most expensive item in your engineering bill—like, obviously, cloud infrastructure, number one—number two and number three is probably observability. How can you not have a strategy for that? How can this be something the board asks you about, and you're like, “What are we trying to get out of this? What's our purpose?” “Uhhhh… troubleshooting?”Corey: Right because it turns into business metrics as well. It's not just about is the site up or not. There's a—like, one of the things that always drove me nuts not just in the observability space, but even in cloud costing is where, okay, your costs have gone up this week so you get a frowny face, or it's in red, like traffic light coloring. Cool, but for a lot of architectures and a lot of customers, that's because you're doing a lot more volume. That translates directly into increased revenues, increased things you care about. You don't have the position or the context to say, “That's good,” or, “That's bad.” It simply is. And you can start deriving business insight from that. And I think that is the real observability story that I think has largely gone untold at tech conferences, at least.Rachel: It's so right. I mean, spending more on something is not inherently bad if you're getting more value out of it. And it definitely a challenge on the cloud cost management side. “My costs are going up, but my revenue is going up a lot faster, so I'm okay.” And I think some of the plays, like you know, we put observability in this box of, like, it's for low-level troubleshooting, but really, if you step back and think about it, there's a lot of larger, bigger picture initiatives that observability can contribute to in an org, like digital transformation. I know that's a buzzword, but, like that is a legit thing that a lot of CTOs are out there thinking about. Like, how do we, you know, get out of the tech debt world, and how do we get into cloud-native?Maybe it's developer efficiency. God, there's a lot of people talking about developer efficiency. Last week at KubeCon, that was one of the big, big topics. I mean, and yeah, what [laugh] what about cost savings? To me, we've put observability in a smaller box, and it needs to bust out.And I see this also in our customer base, you know? Customers like DoorDash use observability, not just to look at their infrastructure and their applications, but also look at their business. At any given minute, they know how many Dashers are on the road, how many orders are being placed, cut by geos, down to the—actually down to the second, and they can use that to make decisions.Corey: This is one of those things that I always found a little strange coming from the world of running systems in large [unintelligible 00:17:28] environments to fixing AWS bills. There's nothing that even resembles a fast, reactive response in the world of AWS billing. You wind up with a runaway bill, they're going to resolve that over a period of weeks, on Seattle business hours. If you wind up spinning something up that creates a whole bunch of very expensive drivers behind your bill, it's going to take three days, in most cases, before that starts showing up anywhere that you can reasonably expect to get at it. The idea of near real time is a lie unless you want to start instrumenting everything that you're doing to trap the calls and then run cost extrapolation from there. That's hard to do.Observability is a very different story, where latencies start to matter, where being able to get leading indicators of certain events—be a technical or business—start to be very important. But it seems like it's so hard to wind up getting there from where most people are. Because I know we like to talk dismissively about the past, but let's face it, conference-ware is the stuff we're the proudest of. The reality is the burning dumpster of regret in our data centers that still also drives giant piles of revenue, so you can't turn it off, nor would you want to, but you feel bad about it as a result. It just feels like it's such a big leap.Rachel: It is a big leap. And I think the very first step I would say is trying to get to this point of clarity and being honest with yourself about where you're at and where you want to be. And sometimes not making a choice is a choice, right, as well. So, sticking with the status quo is making a choice. And so, like, as we get into things like the holiday season right now, and I know there's going to be people that are on-call 24/7 during the holidays, potentially, to keep something that's just duct-taped together barely up and running, I'm making a choice; you're make a choice to do that. So, I think that's like the first step is the kind of… at least acknowledging where you're at, where you want to be, and if you're not going to make a change, just understanding the cost and being realistic about it.Corey: Yeah, being realistic, I think, is one of the hardest challenges because it's easy to wind up going for the aspirational story of, “In the future when everything's great.” Like, “Okay, cool. I appreciate the need to plant that flag on the hill somewhere. What's the next step? What can we get done by the end of this week that materially improves us from where we started the week?” And I think that with the aspirational conference-ware stories, it's hard to break that down into things that are actionable, that don't feel like they're going to be an interminable slog across your entire existing environment.Rachel: No, I get it. And for things like, you know, instrumenting and adding tracing and adding OTEL, a lot of the time, the return that you get on that investment is… it's not quite like, “I put a dollar in, I get a dollar out,” I mean, something like tracing, you can't get to 60% instrumentation and get 60% of the value. You need to be able to get to, like, 80, 90%, and then you'll get a huge amount of value. So, it's sort of like you're trudging up this hill, you're charging up this hill, and then finally you get to the plateau, and it's beautiful. But that hill is steep, and it's long, and it's not pretty. And I don't know what to say other than there's a plateau near the top. And those companies that do this well really get a ton of value out of it. And that's the dream, that we want to help customers get up that hill. But yeah, I'm not going to lie, the hill can be steep.Corey: One thing that I find interesting is there's almost a bimodal distribution in companies that I talk to. On the one side, you have companies like, I don't know, a Chronosphere is a good example of this. Presumably you have a cloud bill somewhere and the majority of your cloud spend will be on what amounts to a single application, probably in your case called, I don't know, Chronosphere. It shares the name of the company. The other side of that distribution is the large enterprise conglomerates where they're spending, I don't know, $400 million a year on cloud, but their largest workload is 3 million bucks, and it's just a very long tail of a whole bunch of different workloads, applications, teams, et cetera.So, what I'm curious about from the Chronosphere perspective—or the product you have, not the ‘you' in this metaphor, which gets confusing—is, it feels easier to instrument a Chronosphere-like company that has a primary workload that is the massive driver of most things and get that instrumented and start getting an observability story around that than it does to try and go to a giant company and, “Okay, 1500 teams need to all implement this thing that are all going in different directions.” How do you see it playing out among your customer base, if that bimodal distribution holds up in your world?Rachel: It does and it doesn't. So, first of all, for a lot of our customers, we often start with metrics. And starting with metrics means Prometheus. And Prometheus has hundreds of exporters. It is basically built into Kubernetes. So, if you're running Kubernetes, getting Prometheus metrics out, actually not a very big lift. So, we find that we start with Prometheus, we start with getting metrics in, and we can get a lot—I mean, customers—we have a lot of customers that use us just for metrics, and they get a massive amount of value.But then once they're ready, they can start instrumenting for OTEL and start getting traces in as well. And yeah, in large organizations, it does tend to be one team, one application, one service, one department that kind of goes at it and gets all that instrumented. But I've even seen very large organizations, when they get their act together and decide, like, “No, we're doing this,” they can get OTel instrumented fairly quickly. So, I guess it's, like, a lining up. It's more of a people issue than a technical issue a lot of the time.Like, getting everyone lined up and making sure that like, yes, we all agree. We're on board. We're going to do this. But it's usually, like, it's a start small, and it doesn't have to be all or nothing. We also just recently added the ability to ingest events, which is actually a really beautiful thing, and it's very, very straightforward.It basically just—we connect to your existing other DevOps tools, so whether it's, like, a Buildkite, or a GitHub, or, like, a LaunchDarkly, and then anytime something happens in one of those tools, that gets registered as an event in Chronosphere. And then we overlay those events over your alerts. So, when an alert fires, then first thing I do is I go look at the alert page, and it says, “Hey, someone did a deploy five minutes ago,” or, “There was a feature flag flipped three minutes ago,” I solved the problem right then. I don't think of this as—there's not an all or nothing nature to any of this stuff. Yes, tracing is a little bit of a—you know, like I said, it's one of those things where you have to make a lot of investment before you get a big reward, but that's not the case in all areas of observability.Corey: Yeah. I would agree. Do you find that there's a significant easy, early win when customers start adopting Chronosphere? Because one of the problems that I've found, especially with things that are holistic, and as you talk about tracing, well, you need to get to a certain point of coverage before you see value. But human psychology being what it is, you kind of want to be able to demonstrate, oh, see, the Meantime To Dopamine needs to come down, to borrow an old phrase. Do you find that some of there's some easy wins that start to help people to see the light? Because otherwise, it just feels like a whole bunch of work for no discernible benefit to them.Rachel: Yeah, at least for the Chronosphere customer base, one of the areas where we're seeing a lot of traction this year is in optimizing the costs, like, coming back to the cost story of their overall observability bill. So, we have this concept of the control plane in our product where all the data that we ingest hits the control plane. At that point, that customer can look at the data, analyze it, and decide this is useful, this is not useful. And actually, not just decide that, but we show them what's useful, what's not useful. What's being used, what's high cardinality, but—and high cost, but maybe no one's touched it.And then we can make decisions around aggregating it, dropping it, combining it, doing all sorts of fancy things, changing the—you know, downsampling it. We can do this, on the trace side, we can do it both head based and tail based. On the metrics side, it's as it hits the control plane and then streams out. And then they only pay for the data that we store. So typically, customers are—they come on board and immediately reduce their observability dataset by 60%. Like, that's just straight up, that's the average.And we've seen some customers get really aggressive, get up to, like, in the 90s, where they realize we're only using 10% of this data. Let's get rid of the rest of it. We're not going to pay for it. So, paying a lot less helps in a lot of ways. It also helps companies get more coverage of their observability. It also helps customers get more coverage of their overall stack. So, I was talking recently with an autonomous vehicle driving company that recently came to us from the Dog, and they had made some really tough choices and were no longer monitoring their pre-prod environments at all because they just couldn't afford to do it anymore. It's like, well, now they can, and we're still saving the money.Corey: I think that there's also the downstream effect of the money saving to that, for example, I don't fix observability bills directly. But, “Huh, why is your CloudWatch bill through the roof?” Or data egress charges in some cases? It's oh because your observability vendor is pounding the crap out of those endpoints and pulling all your log data across the internet, et cetera. And that tends to mean, oh, yeah, it's not just the first-order effect; it's the second and third and fourth-order effects this winds up having. It becomes almost a holistic challenge. I think that trying to put observability in its own bucket, on some level—when you're looking at it from a cost perspective—starts to be a, I guess, a structure that makes less and less sense in the fullness of time.Rachel: Yeah, I would agree with that. I think that just looking at the bill from your vendor is one very small piece of the overall cost you're incurring. I mean, all of the things you mentioned, the egress, the CloudWatch, the other services, it's impacting, what about the people?Corey: Yeah, it sure is great that your team works for free.Rachel: [laugh]. Exactly, right? I know, and it makes me think a little bit about that viral story about that particular company with a certain vendor that had a $65 million per year observability bill. And that impacted not just them, but, like, it showed up in both vendors' financial filings. Like, how did you get there? How did you get to that point? And I think this all comes back to the value in the ROI equation. Yes, we can all sit in our armchairs and be like, “Well, that was dumb,” but I know there are very smart people out there that just got into a bad situation by kicking the can down the road on not thinking about the strategy.Corey: Absolutely. I really want to thank you for taking the time to speak with me about, I guess, the bigger picture questions rather than the nuts and bolts of a product. I like understanding the overall view that drives a lot of these things. I don't feel I get to have enough of those conversations some weeks, so thank you for humoring me. If people want to learn more, where's the best place for them to go?Rachel: So, they should definitely check out the Chronosphere website. Brand new beautiful spankin' new website: chronosphere.io. And you can also find me on LinkedIn. I'm not really on the Twitters so much anymore, but I'd love to chat with you on LinkedIn and hear what you have to say.Corey: And we will, of course, put links to all of that in the [show notes 00:28:26]. Thank you so much for taking the time to speak with me. It's appreciated.Rachel: Thank you, Corey. Always fun.Corey: Rachel Dines, Head of Product and Solutions Marketing at Chronosphere. This has been a featured guest episode brought to us by our friends at Chronosphere, and I'm Corey Quinn. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry and insulting comment that I will one day read once I finished building my highly available rsyslog system to consume it with.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business, and we get to the point. Visit duckbillgroup.com to get started.

Observability software helps teams to actively monitor and debug their systems, and these tools are increasingly vital in DevOps. However, it's not uncommon for the volume of observability data to exceed the amount of actual business data. This creates two challenges – how to analyze the large stream of observability data, and how to keep The post Chronosphere with Martin Mao appeared first on Software Engineering Daily.

Martin Mao, CEO & Cofounder at Chronosphere, joins Corey on Screaming in the Cloud to discuss the trends he sees in the observability industry. Martin explains why he feels measuring observability costs isn't nearly as important as understanding the velocity of observability costs increasing, and why he feels efficiency is something that has to be built into processes as companies scale new functionality. Corey and Martin also explore how observability can now be used by business executives to provide top line visibility and value, as opposed to just seeing observability as a necessary cost. About MartinMartin is a technologist with a history of solving problems at the largest scale in the world and is passionate about helping enterprises use cloud native observability and open source technologies to succeed on their cloud native journey. He's now the Co-Founder & CEO of Chronosphere, a Series C startup with $255M in funding, backed by Greylock, Lux Capital, General Atlantic, Addition, and Founders Fund. He was previously at Uber, where he led the development and SRE teams that created and operated M3. Previously, he worked at AWS, Microsoft, and Google. He and his family are based in the Seattle area, and he enjoys playing soccer and eating meat pies in his spare time.Links Referenced: Chronosphere: https://chronosphere.io/ LinkedIn: https://www.linkedin.com/in/martinmao/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Human-scale teams use Tailscale to build trusted networks. Tailscale Funnel is a great way to share a local service with your team for collaboration, testing, and experimentation.  Funnel securely exposes your dev environment at a stable URL, complete with auto-provisioned TLS certificates. Use it from the command line or the new VS Code extensions. In a few keystrokes, you can securely expose a local port to the internet, right from the IDE.I did this in a talk I gave at Tailscale Up, their first inaugural developer conference. I used it to present my slides and only revealed that that's what I was doing at the end of it. It's awesome, it works! Check it out!Their free plan now includes 3 users & 100 devices. Try it at snark.cloud/tailscalescream Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This promoted guest episode is brought to us by our friends at Chronosphere. It's been a couple of years since I got to talk to their CEO and co-founder, Martin Mao, who is kind enough to subject himself to my slings and arrows today. Martin, great to talk to you.Martin: Great to talk to you again, Corey, and looking forward to it.Corey: I should probably disclose that I did run into you at Monitorama a week before this recording. So, that was an awful lot of fun to just catch up and see people in person again. But one thing that they started off the conference with, in the welcome-to-the-show style of talk, was the question about benchmarking: what observability spend should be as a percentage of your infrastructure spent. And from my perspective, that really feels a lot like a question that looks like, “Well, how long should a piece of string be?” It's always highly contextual.Martin: Mm-hm.Corey: Agree, disagree, or are you hopelessly compromised because you are, in fact, an observability vendor, and it should always be more than it is today?Martin: [laugh]. I would say, definitely agree with you from a exact number perspective. I don't think there is a magic number like 13.82% that this should be. It definitely depends on the context of how observability is used within a company, and really, ultimately, just like anything else you pay for, it really gets derived from the value you get out of it. So, I feel like if you feel like you're getting the value out of it, it's sort of worth the dollars that you put in.I do see why a lot of companies out there and people are interested because they're trying to benchmark, to trying to see, am I doing best practice? So, I do think that there are probably some best practice ranges that I'd say most typical organizations out there that we see. This is one thing I'd say. The other thing I'd say when it comes to observability costs is one of the concerns we've seen talking with companies is that the relative proportion of that cost to the infrastructure is rising over time. And that's probably a bad sign for companies because if you extrapolate, you know, if the relative cost of observability is growing faster than infrastructure, and you extrapolate that out a few years, then the direction in which this is going is bad. So, it's probably more the velocity of growth than the absolute number that folks should be worried about.Corey: I think that that is probably a fair assessment. I get it all the time, at least in years past, where companies will say, “For every 1000 daily active users, what should it cost to service them?” And I finally snapped in one of my talks that I gave at DevOps Enterprise Summit, and said, I think it was something like $7.34.Martin: [laugh]. Right, right.Corey: It's an arbitrary number that has no context on your business, regardless of whether those users are, you know, Twitter users or large banks you have partnerships with. But now you have something to cite. Does it help you? Not really. But we'll it get people to leave you alone and stop asking you awkward questions?Martin: Right, right.Corey: Also not really, but at least now you have a number.Martin: Yeah, a hundred percent. And again, like I said, there's no—and glad magic numbers weren't too far away from each other. But yeah, I mean, there's no exact number there, for sure. One pattern I've been seeing more recently is, like, rather than asking for the number, there's been a lot more clarity in companies on figuring out, “Well, okay, before even pick what the target should be, how much am I spending on this per whatever unit of efficiency is?” Right?And generally, that unit of efficiency, I've actually seen it being mapped more to the business side of things, so perhaps to the number of customers or to customer transactions and whatnot. And those things are generally perhaps easier to model out and easier to justify as opposed to purely, you know, the number of seats or the number of end-users. But I've seen a lot more companies at least focus on the measurement of things. And again, it's been more about this sort of, rather than the absolute number, the relative change in number because I think a lot of these companies are trying to figure out, is my business scaling in a linear fashion or sub-linear fashion or perhaps an exponential fashion, if it's—the costs are, you know, you can imagine growing exponentially, that's a really bad thing that you want to get ahead of.Corey: That I think is probably the real question people are getting at is, it seems like this number only really goes up and to the right, it's not something that we have any real visibility into, and in many cases, it's just the pieces of it that rise to the occasion. A common story is someone who winds up configuring a monitoring system, and they'll be concerned about how much they're paying that vendor, but ignore the fact that, well, it's beating up your CloudWatch API charges all the time on this other side as well, and data egress is not free—surprise, surprise. So, it's the direct costs, it's the indirect costs. And the thing people never talk about, of course, is the cost of people to feed and maintain these systems.Martin: Yeah, a hundred percent, you're spot on. There's the direct costs, there's the indirect costs. Like you mentioned, in observability, network egress is a huge indirect cost. There's the people that you mentioned that need to maintain these systems. And I think those are things that companies definitely should take into account when they think about the total cost of ownership there.I think what's more in observability actually is, and this is perhaps a hard thing to measure, as well, is often we ask companies, “Well, what is the cost of downtime?” Right? Like if you're, if your business is impacted and your customers are impacted and you're down, what is the cost of each additional minute of downtime, perhaps, right? And then the effectiveness of the tool can be evaluated against that because you know, observability is one of these, it's not just any other developer tool; it's the thing that's giving you insight into, is my business or my product or my service operating in the way that I intend. And, you know, is my infrastructure up, for example, as well, right? So, I think there's also the piece of, like, what is the tool really doing in terms of, like, a lost revenue or brand impact? Those are often things that are sort of quite easily overlooked as well.Corey: I am curious to see whether you have noticed a shifting in the narrative lately, where, as someone who sells AWS cost optimization consulting as a service, something that I've noticed is that until about a year ago, no one really seemed to care overly much about what the AWS bill was. And suddenly, my phone's been ringing off the hook. Have you found that the same is true in the observability space, where no one really cared what the observability cost, until suddenly, recently, everyone does or has this been simmering for a while?Martin: We have found that exact same phenomenon. And what I tell most companies out there is, we provide an observability platform that's targeted at cloud-native platforms. So, if your—a cloud-native architecture, so if you're running microservices-oriented architecture on containers, that's the type of architecture that we've optimized our solution for. And historically, we've always done two things to try to differentiate: one is, provide a better tool to solve that particular problem in that particular architecture, and the second one is to be a more cost-efficient solution in doing so. And not just cost-efficient, but a tool that shows you the cost and the value of the data that you're storing.So, we've always had both sides of that equation. And to your point, in conversations in the past years, they've generally been led with, “Look, I'm looking for a better solution. If you just happen to be cheaper, great. That's a nice cherry on top.” Whereas this year, the conversations have flipped 180, in which case, most companies are looking for a more cost-efficient solution. If you just happen to be a better tool at the same time, that's more of a nice-to-have than anything else. So, that conversation has definitely flipped 180 for us. And we found a pretty similar experience to what you've been seeing out in the market right now.Corey: Which makes a tremendous amount of sense. I think that there's an awful lot of—oh, we'll just call it strangeness, I think. That's probably the best way to think about it—in terms of people waking up to the grim reality that not caring about your bills was functionally a zero-interest-rate phenomenon in the corporate sense. Now, suddenly, everyone really has to think about this in some unfortunate and some would say displeasing ways.Martin: Yeah, a hundred percent. And, you know, it was a great environment for tech for over a decade, right? So, it was an environment that I think a lot of companies and a lot of individuals got used to, and perhaps a lot of folks that have entered the market in the last decade don't know of another situation or another set of conditions where, you know, efficiency and cost really do matter. So, it's definitely top of mind, and I do think it's top of mind for good reason. I do think a lot of companies got fairly inefficient over the last few years chasing that top-line growth.Corey: Yeah, that has been—and I think it makes sense in the context with which people were operating. Because before a lot of that wound up hitting, it was, well grow, grow, grow at all costs. “What do you mean you're not doing that right now? You should be doing that right now. Are you being irresponsible? Do we need to come down there and talk to you?”Martin: A hundred percent.Corey: Yeah, it's like eating your vegetables. Now, it's time to start paying attention to this.Martin: Yeah, a hundred percent. It's always a trade-off, right? It's like in an individual company and individual team, you only have so many resources and prioritization. I do think, to your point, in a zero interest environment, trying to grow that top line was the main thing to do, and hence, everything was pushed on how quickly can we deliver new functionality, new features, or grow that top line. Whereas, the efficiency is always something I think a lot of companies looked at as something I can go deal with later on and go fix. And you know, I feel like that that time has now just come.Corey: I will say that I somewhat recently had the distinct privilege of working with a company whose observability story was effectively, “We wait for customers to call and tell us there's a problem and then we go looking in into it.” And on the one hand, my immediate former SRE reflexes kicked in, and I recoiled, but this company has been in this industry longer than I have. They clearly have a model that is working for them and for their customers. It's not the way I would build something, but it does seem that for some use cases, you absolutely are going to be okay with something like that. And I should probably point out, they were not, for example, a bank where yeah, you kind of want to get some early warning on things that could destabilize the economy.Martin: Right, right. I mean, to your point, depending on the context, and the company, it could definitely make sense, and depending on how they execute it as well, right? So, you know, you called out an example already, where if they were a bank or if any correctness or timeliness of a response was important to that business, perhaps not the best thing to do to have your customers find out, especially if you have a ton of customers at the same time. But however, you know, if it's a different type of business where, you know, the responses are perhaps more asynchronous or you don't have a lot of users encountering at the same time or perhaps you have a great A/B experimentation platform and testing platform, you know, there are definitely conditions in which that could be potentially a viable option.Especially when you weigh up the cost and the benefit, right? If the cost to having a few bad customers have a bad experience is not that much to the business and the benefit is that you don't have to spend a ton on observability, perhaps that's a trade-off that the company is willing to make. In most of the businesses that we've been working with, I would say that probably not been the case, but I do think that there's probably some bias and some skew there in the sense that you can imagine a company that cares about these things, perhaps it's more likely to talk to an observability vendor like us to try to fix these problems.Corey: When we spoke a few years back, you definitely were focused on the large, one would say, almost hyperscale style of cloud-native build-out. Is that still accurate or has the bar to entry changed since we last spoke? I know you've raised an awful lot of money, which good for you. It's a sign of a healthy, robust VC ecosystem. What the counterpoint to that is, they're probably not investing in a company whose total addressable market is, like, 15 companies that must be at least this big.Martin: [laugh]. Yeah, a hundred percent. A hundred percent. So, I'll tell you that the bar to entry definitely has changed, but it's not due to a business decision on our end. If you think about how we started and, you know, the focus area, we're really targeting accounts that are adopting cloud-native technology.And it just so happens that the large tech, [decacorns 00:12:35], and the hyperscalers were the earliest adopters of cloud-native. So containerization, microservices, they were the earliest adopters of that, so hence, there was a high correlation in the companies that had that problem and the companies that we could serve. Luckily, for us, the trend has been that more of the rest of the industry has gone down this route as well. And it's not just new startups; you can imagine any new startup these days probably starts off cloud-native from day one, but what we're finding is the more established, larger enterprises are doing this shift as well. And I think the folks out there like Gartner have studied this and predicted that, you know, by about 2028, I believe was the date, about 95% of applications are going to be containerized in large enterprises. So, it's definitely a trend that the rest of the industry will go on. And as they continue down that trend, that's when, sort of, our addressable market will grow because the amount of use cases where our technology shines will grow along with that as well.Corey: I'm also curious about your description of being aimed at cloud-native companies. You gave one example of microservices powered by containers, if I understood correctly. What are the prerequisites for this? When you say that it almost sounds like you're trying to avoid defining a specific architecture that you don't want to deal well with or don't want to support for a variety of reasons? Is that what it is or is there certain you must be built in these ways or the product does not work super well for you? What is it you're trying to say with that, is what I'm trying to get at here.Martin: Yeah, a hundred percent. If you look at the founding story here, it's really myself and my co-founder, found Uber going through this transition of both a new architecture, in the sense that, you know, they were going containers, they were building microservices-oriented architecture there, were also adopting a DevOps mentality as well. So, it was just a new way of building software, almost. And what we found is that when you develop software in this particular way—so you can imagine when you're developing a tiny piece of functionality as a microservice and you're a individual developer, and you're—you know, you can imagine rolling that out into production multiple times a day, in that way of developing software, what we found was that the traditional tools, the application performance monitoring tools, the IT monitoring tools that used to exist pre this way of both architecture and way of developing software just weren't a good fit.So, the whole reason we exist is that we had to figure out a better way of solving this particular problem for the way that Uber built software, which was more of a cloud-native approach. And again, it just so happens that the rest of the industry is moving down this path as well and hence, you know, that problem is larger for a larger portion of the companies out there. You know, I would say some of the things when you look into why the existing solutions can't solve these problems well, you know, if you look at a application performance monitoring tool, an APM tool, it's really focused on introspecting into that application and its interaction with the operating system or the underlying hardware. And yet, these days, that is less important when you're running inside the container. Perhaps you don't even have access to the underlying hardware, or the operating system and what you care about—you can imagine—is how that piece of functionality interacts with all the other pieces of functionality out there, over a network core.So, just the architecture and the conditions ask for a different type of observability, a different type of monitoring, and hence, you just need a different type of solution to go solve for this new world. Along with this, which is sort of related to the cost as well, is that, you know, as we go from virtual machines onto containers, you can imagine the sheer volume of data that gets produced now because everything is much smaller than it was before and a lot more ephemeral than it was before, and hence, every small piece of infrastructure, every small piece of code, you can imagine still needs as much monitoring and observability as it did before, as well. So, just the sheer volume of data is so much larger for the same amount of infrastructure, for the same amount of hardware that that you used to have, and that's really driving a huge problem in terms of being able to scale for it and also being able to pay for these systems as well.Corey: Tired of Apache Kafka's complexity making your AWS bill look like a phone number? Enter Redpanda. You get 10x your streaming data performance without having to rob a bank. And migration? Smoother than a fresh jar of peanut butter. Imagine cutting as much as 50% off your AWS bills. With Redpanda, it's not a dream, it's reality. Visit go.redpanda.com/duckbill. Redpanda: Because Kafka shouldn't cause you nightmares.Corey: I think that there's a common misconception in the industry that people are going to either have ancient servers rotting away in racks, or they're going to build something greenfield, the way that we see done on keynote stage is all the time of companies that have been around with this architecture for less than 18 months. In practice, I find it's awfully frequent that this is much more of a spectrum, and a case-by-case per-workload basis. I haven't met too many data center companies where everything's the disaster that the cloud companies like to paint it as, and vice versa, I also have never yet seen a architecture that really existed as described in a keynote presentation.Martin: A hundred percent agree with you there. And you know, it's not clean-cut from that perspective. And also, you're also forgetting the messy middle as well, right? Like, often what happens is, there's a transition. If you don't start off cloud-native from day one, you do need to transition there from your monolithic applications, from your VM-based architectures, and often the use case can't transform over perfectly.What ends up happening is you start moving some functionality and containerizing some functionality and that still has dependencies between the old architecture and the new architecture. And companies have to live in this middle state, perhaps for a very long time. So, it's definitely true. It's not a clean-cut transition. But you can think about that middle state is actually one that a lot of companies struggle with because all of a sudden, you only have a partial view of the world, or what's happening with your old tools, they're not well suited for the new environments. Perhaps you got to start bringing new tools and new ways of doing things in your new environments, and they're not perhaps the best suited for the old environment as well.So, you do actually end up in this middle state where you need a good solution that can really handle both because there are a lot of interdependencies between the two. And it's actually one of the things that we strive to do here at Chronosphere is to help companies through that transition. So, it's not just all of the new use cases and it's not just all of your new environments. It's actually helping companies through this transition is actually pretty critical as well.Corey: My question for you is, given that you have, I don't want to say a preordained architecture that your customers have to use, but there are certain assumptions you've made based upon both their scale and the environment in which they're operating. How heavy of a lift is it for them to wind up getting Chronosphere into their environments? Just because seems to me that it's not that hard to design an architecture on a whiteboard that can meet almost any requirement. The messy part is figuring out how to get something that resembles that into place on a pre-existing, extant architecture.Martin: Yeah. I'd say it's something we spent a lot of time on. The good thing for the industry overall, for the observability industry, is that open-source standards are now created and now exist when they didn't before. So, if you look at the APM-based view, it was all proprietary agents producing the data themselves that would only really work with one vendor product, whereas if you've look at a modern environment, the production of the data has actually been shifted from the vendor down to the companies themselves, and there'll be producing these pieces of data in open-source standard formats like OpenTelemetry for distributed traces, or perhaps Prometheus for metrics.So, the good thing is that for all of the new environments, there's a standard way to produce all of this data and you can send all that data to whichever vendor you want on the back end. So, it just makes the implementation for the new environments so much easier. Now, for the legacy environments, or if a company is shifting over from an existing tool, there is actually a messy migration there because often you're trying to replace proprietary formats and proprietary ways of producing data with open-source standard ones. So, just something that us as Chronosphere just come in and we view that as a particular problem that we need to solve and we take the responsibility of solving for a company because what we're trying to sell companies is not just a tool, what we're really trying to solve them is the solution to the problem, and the problem is they need an observability solution end to end. So, this often involves us coming in and helping them, you can imagine, not just convert the data types over but also move over existing dashboards, existing alerts.There's a huge piece of lift that the end—that perhaps every developer in a company would have to do if we didn't come in and do it on behalf of those companies. So, it's just an additional responsibility. It's not an easy thing to do. We've built some tooling that helps with it, and we just spend a lot of manual hours going through this, but it's a necessary one in order to help a company transition. Now, the good thing is, once they have transitioned into the new way of doing things and they are dependent on open-source standard formats, they are no longer locked in. So, you know, you can imagine future transitions will be much easier, however the current one does have to go through a little bit of effort.Corey: I think that's probably fair. And then there's no such thing, in my experience, as a easy deployment for something that is large enough to matter. And let's be clear, people are not going to be deploying something as large scale as Chronosphere on a lark. This is going to be when they have a serious application with serious observability challenges. So, it feels like, on some level, that even doing a POC is a tricky proposition, just due to the instrumentation part of it. Something I've seen is that very often, enterprise sales teams will decide that by the time that they can get someone to successfully pull off a POC, at that point, the deal win rate is something like 95% just because no one wants to try that in a bake-off with something else.Martin: Yeah, I'd say that we do see high pilot conversion rates, to your point. For us, it's perhaps a little bit easier than other solutions out there, in the sense that I think with our type of observability tooling, the good thing is, an individual team could pick this up for their one use case and they could get value out of it. It's not that every team across an environment or every team in an organization needs to adopt. So, while generally, we do see that, you know, a company would want to pilot and it's not something you can play around online with by yourself because it does need a particular deployment, it does need a little bit of setup, generally one single team can come and perform that and see value out of the tool. And that sort of value can be extrapolated and applied to all the other teams as well. So, you're correct, but it hasn't been a huge lift. And you know, these processes end to end, we've seen be as short as perhaps 30-something days end to end, which is generally a pretty fast-moving process there.Corey: Now, I guess, on some level, I'm still trying to wrap my head around the idea of the scale that you operate at, just because as you mentioned, this came out of Uber—which is beyond imagining for most people—and you take a look at a wide variety of different use cases. And in my experience it's never been, “Holy crap, we have no observability and we need to fix that.” It's, “There are a variety of systems in place that just are not living up to the hopes, dreams, and potential that they had when they were originally deployed.” Either due to growth or due to lack of product fit, or the fact that it turns out in a post zero-interest-rate world, most people don't want to have a pipeline of 20 discrete observability tools.Martin: Yep, yep. No, a hundred percent. And, to your point there, ultimately, it's our goal and, you know, in many companies were replacing up to six to eight tools in a single platform. And so, it's great to do. That definitely doesn't happen overnight. It takes time.You know, you can imagine in a pilot or when you're looking at it, we're picking a few of the use cases to demonstrate what our tool could do across many other use cases, and then generally on the onboarding, during the onboarding time or perhaps over a period of months or perhaps even a year plus, we then go on board these use cases a piece by piece. So, it's definitely not a quick overnight process there, but, you know, you can imagine something that can help each end developer in that particular company be more effective and it's something that can really help move the bottom line in terms of far better price efficiency. These things are generally not things that are quick fixes; these are generally things that do take some time and a little bit of investment to achieve the results.Corey: So, a question I do have for you, given that I just watched an awful lot of people talking about observability for three days at Monitorama, what are people not talking about? What did you not see discussed that you think should be?Martin: Yeah, one thing I think often gets overlooked, and especially in today's climate is, I think observability gets relegated to a cost center. It's something that every company must have, every company has today, and it's often looked at a tool that gives you insights about your infrastructure and your applications and it's a backend tool, something you have to have, something you have to pay for and it doesn't really move the direct needle for the business top line. And I think that's often something that companies don't talk about enough. And you know, from our experience at Uber and through most of the companies that we work with here at Chronosphere, yes, there are infrastructure problems and application level problems that we help companies solve, but ultimately, the more mature organizations, or when it comes to observability, are often starting to get real-time insights into the business more than the application layer and the infrastructure layer.And if you think about it, companies that are cloud-native architected, there's not one single endpoint or one single application that fulfills a single customer request. So, even if you could look at all the individual pieces, the actual what we have to do for customers in our products and services span across so many of them that often you need to introduce a new view, a view that's just focused on your customers, just focused on the business, and sort of apply the same type of techniques on your backend infrastructure as you do for your business. Now, this isn't a replacement for your BI tools, you still need those, but what we find is that BI tools are more used for longer-term strategic decisions, whereas you may need to do a lot of sort of tactical, more tactical, business operational functions based on having a live view of the business. So, what we find is often observability is only ever thought about for infrastructure, it's only ever thought about as a cost center, but ultimately observability tooling can actually add a lot directly to your top line by giving you visibility into the products and services that make up that top line. And I would say the more mature organizations that we work with here at Chronosphere all had their executives looking at, you know, monitoring dashboards to really get a good sense of what's happening in their business in real-time. So, I think that's something that hopefully a lot more companies evolve into over time and they really see the full benefit of observability and what it can do to a business's top line.Corey: I think that's probably a fair way of approaching it. It seems similar, in some respects, to what I tend to see over in the cloud cost optimization space. People often want to have something prescriptive of, do this, do that do the other thing, but it depends entirely what the needs of the business are internally, it depends upon the stories that they wind up working with, it depends really on what their constraints are, what their architectures are doing. Very often it's a let's look and figure out what's going on and accidentally, they discover they can blow 40% off their spend by just deleting things that aren't in use anymore. That becomes increasingly uncommon with scale, but it's still one of those questions of, “What do we do here and how?”Martin: Yep, a hundred percent.Corey: I really want to thank you for taking the time to speak with me today about what you're seeing. If people want to learn more, where's the best place for them to find you?Martin: Yeah, the best place is probably going to our website Chronosphere.io to find out more about the company, or if you want to chat with me directly, LinkedIn is probably the best place to come find me, via my name.Corey: And we will, of course, put links to both of those things in the [show notes 00:28:49]. Thank you so much for suffering the slings and arrows I was able to throw at you today.Martin: Thank you for having me Corey. Always a pleasure to speak with you, and looking forward to our next conversation.Corey: Likewise. Martin Mao, CEO and co-founder of Chronosphere. This promoted guest episode has been brought to us by Chronosphere, here on Screaming in the Cloud. And I'm Cloud Economist Corey Quinn. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an insulting comment that I will never notice because I have an observability gap.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Martin Mao is the co-founder and CEO of Chronosphere, the provider of the leading observability platform for cloud-native. He previously held roles at leading tech companies including Uber, Microsoft, Google and Amazon. Top 3 Value Bombs: 1. Luck and timing play a significant role in the result of your success. 2. More industries are now adopting the same technology, and Chronosphere is there to provide better solutions. 3. Be ready when an opportunity presents itself. Take a step back, look at more significant trends in your economy and industry, and be prepared to capitalize on these opportunities. Visit and take back control of Observability - Chronosphere Website  Sponsor: HubSpot: A platform that's easy for your entire team to use! Learn how HubSpot can make it easier for your business to grow better at Hubspot.com!