text
stringlengths
0
2.35k
[2924.68 --> 2925.94] in our pull requests all the time.
[2926.40 --> 2927.60] That's part of being an engineer.
[2927.60 --> 2956.08] This episode is brought to you by Honeycomb.
[2956.08 --> 2957.48] Don't find your most perplexing
[2957.48 --> 2958.56] application issues.
[2958.86 --> 2961.68] Honeycomb is a fast analysis tool
[2961.68 --> 2962.58] that reveals the truth
[2962.58 --> 2963.88] about every aspect
[2963.88 --> 2965.78] of your application in production.
[2966.20 --> 2967.26] Find out how users experience
[2967.26 --> 2968.54] your code in complex
[2968.54 --> 2970.24] and unpredictable environments.
[2970.50 --> 2971.28] Find patterns
[2971.28 --> 2972.28] and outliers
[2972.28 --> 2973.90] across billions of rows of data
[2973.90 --> 2975.50] and definitively solve your problems.
[2975.86 --> 2976.62] And we use Honeycomb
[2976.62 --> 2977.36] here at Change.
[2977.40 --> 2977.48] Well,
[2977.48 --> 2978.02] that's why we welcome
[2978.02 --> 2979.42] the opportunity to add them
[2979.42 --> 2981.22] as one of our infrastructure partners.
[2981.22 --> 2982.22] In particular,
[2982.22 --> 2983.12] we use Honeycomb
[2983.12 --> 2984.86] to track down CDN issues recently,
[2984.86 --> 2986.60] which we talked about at length
[2986.60 --> 2987.84] on the Kaizen edition
[2987.84 --> 2989.06] of the Ship It podcast.
[2989.32 --> 2989.98] So check that out.
[2990.24 --> 2990.72] Here's the thing.
[2990.96 --> 2992.18] Teams who don't use Honeycomb
[2992.18 --> 2993.32] are forced to find
[2993.32 --> 2994.20] the needle in the haystack.
[2994.32 --> 2995.34] They scroll through
[2995.34 --> 2996.44] endless dashboards
[2996.44 --> 2997.48] playing whack-a-mole.
[2997.70 --> 2998.88] They deal with alert floods,
[2999.10 --> 2999.70] trying to guess
[2999.70 --> 3000.74] which one matters.
[3001.12 --> 3002.06] And they go from tool
[3002.06 --> 3002.92] to tool to tool
[3002.92 --> 3003.74] playing sleuth,
[3004.00 --> 3004.60] trying to figure out
[3004.60 --> 3005.72] how all the puzzle pieces
[3005.72 --> 3006.34] fit together.
[3006.68 --> 3007.94] It's this context switching
[3007.94 --> 3009.04] and tool sprawl
[3009.04 --> 3009.94] that are slowly killing
[3009.94 --> 3011.00] teams effectiveness
[3011.00 --> 3012.36] and ultimately hindering
[3012.36 --> 3013.00] their business.
[3013.40 --> 3013.90] With Honeycomb,
[3014.00 --> 3014.98] you get a fast,
[3015.30 --> 3015.84] unified,
[3016.12 --> 3017.62] and clear understanding
[3017.62 --> 3019.02] of the one thing
[3019.02 --> 3020.16] driving your business.
[3020.42 --> 3020.84] Production.
[3021.36 --> 3021.94] With Honeycomb,
[3022.04 --> 3022.90] you guess less
[3022.90 --> 3023.84] and you know more.
[3024.22 --> 3024.90] Join the swarm
[3024.90 --> 3026.70] and try Honeycomb free today
[3026.70 --> 3028.30] at honeycomb.io
[3028.30 --> 3029.44] slash changelog.
[3029.74 --> 3030.14] Again,
[3030.28 --> 3031.38] honeycomb.io
[3031.38 --> 3033.06] slash changelog.
[3033.28 --> 3034.26] And by our friends
[3034.26 --> 3034.98] at Chronosphere,
[3035.46 --> 3036.18] scaling cloud native
[3036.18 --> 3037.08] is complicated
[3037.08 --> 3038.42] and Chronosphere helps teams
[3038.42 --> 3039.20] take back control
[3039.20 --> 3040.36] of observability,
[3040.76 --> 3041.74] tame rampant data growth,
[3042.04 --> 3043.18] reduce cloud native complexity,
[3043.64 --> 3044.48] and increase confidence
[3044.48 --> 3045.36] of the business.
[3045.82 --> 3046.68] And I'm here with Mark Mow,
[3046.76 --> 3047.86] co-founder and CEO
[3047.86 --> 3048.38] of Chronosphere.
[3048.86 --> 3049.38] Mark, when it comes
[3049.38 --> 3050.62] to cloud native observability,
[3051.02 --> 3052.10] what are the pain points
[3052.10 --> 3052.76] of Kubernetes
[3052.76 --> 3053.96] and making sure
[3053.96 --> 3054.68] it's reliable?
[3055.20 --> 3055.34] You know,
[3055.36 --> 3056.02] I think the shift
[3056.02 --> 3056.52] to Kubernetes
[3056.52 --> 3057.78] has really changed
[3057.78 --> 3059.94] the way we design applications.
[3060.26 --> 3061.80] It's changed the way we,
[3062.04 --> 3063.26] it's changed our infrastructure
[3063.26 --> 3063.74] as well.
[3063.78 --> 3064.22] So it's introduced
[3064.22 --> 3065.02] a lot of change,
[3065.08 --> 3065.48] I would say,
[3065.54 --> 3066.10] and that's probably