text
stringlengths
0
1.8k
[2381.92 --> 2385.18] When your team learns from an incident, you can codify those learnings into repeatable
[2385.18 --> 2386.28] automated runbooks.
[2386.64 --> 2390.88] And these runbooks can create a Slack incident channel, notify particular team members, create
[2390.88 --> 2395.00] tickets, schedule a Zoom meeting, execute a script, or send a web hook.
[2395.32 --> 2396.06] Here's how it works.
[2396.24 --> 2399.98] Your app goes down, an alert gets sent to a specific Slack channel, which can then be
[2399.98 --> 2400.98] turned into an incident.
[2401.36 --> 2404.48] That will trigger a workflow you've created already in a runbook.
[2404.78 --> 2409.44] A pinned message inside Slack will show all the details, the Jira or Clubhouse ticket,
[2409.74 --> 2410.48] the Zoom meeting.
[2410.78 --> 2415.32] And all of this is contained in your dedicated incident channel that everyone on the team
[2415.32 --> 2416.10] pays attention to.
[2416.36 --> 2419.46] Now you're spending less time thinking about what to do next, and you're getting to work
[2419.46 --> 2421.44] actually resolving the issue faster.
[2422.02 --> 2425.70] What would normally be manual tickets across the entire spectrum of responding to an incident
[2425.70 --> 2429.18] can now be automated in every single way with FireHydrant.
[2429.46 --> 2430.56] And here's the best part.
[2430.74 --> 2432.52] You can try it free for 14 days.
[2432.64 --> 2434.40] You get access to every single feature.
[2434.78 --> 2436.02] No credit card required at all.
[2436.28 --> 2439.54] That way you can prove to yourself and your team that this works for you.
[2439.54 --> 2441.98] Get started at FireHydrant.io.
[2442.34 --> 2444.70] Again, FireHydrant.io.
[2444.70 --> 2466.60] I know, Romano, that you have a YouTube channel, which is growing in popularity.
[2466.86 --> 2468.18] I've seen some really good videos.
[2468.18 --> 2475.46] And I've checked today, and your most popular video today is what are the DevOps trends that
[2475.46 --> 2477.12] you have seen in 2021.
[2477.62 --> 2479.80] I think 2021 DevOps trends, something like that.
[2479.86 --> 2482.54] I forget the exact title, but it was DevOps trends for 2021.
[2483.22 --> 2485.70] So why do you think that video is so popular?
[2486.02 --> 2488.94] Actually, I really don't know why it is so popular.
[2488.94 --> 2495.08] But I made some analysis, and it looks like people are Googling this title.
[2495.36 --> 2498.32] So they want to know what the trends are.
[2498.58 --> 2499.12] So what are they?
[2499.22 --> 2500.60] Can you tell us what they are?
[2500.94 --> 2501.54] Yeah, of course.
[2501.74 --> 2508.24] So the trends which I brought up in 2021 was it's all about automation.
[2508.72 --> 2511.02] So we need to automate more.
[2511.02 --> 2514.70] So that's one of the trends that I pointed out.
[2515.04 --> 2515.52] Security.
[2515.88 --> 2520.50] So the whole DevSecOps, that was a huge one.
[2520.88 --> 2525.50] And AIOps, that was also one of the trends that I pointed out.
[2525.74 --> 2529.86] So we have a lot of data, and we need to deal with this data.
[2530.08 --> 2532.96] So AI is a very good match for that.
[2533.26 --> 2536.74] And these are the things that I see are coming up.
[2536.74 --> 2544.02] So when I look back to the statements that I did, I think I was absolutely right with these trends.
[2544.22 --> 2549.72] For example, when I look at AIOps, this is something that's coming quite huge.
[2549.98 --> 2557.72] I also started using AIOps in some areas, and the results are really amazing.
[2558.20 --> 2560.30] First of all, what is AIOps?
[2560.60 --> 2562.84] And second of all, how do you make use of that?
[2562.94 --> 2564.84] What does it look like in practice for you?
[2564.84 --> 2571.36] So AIOps, as I said, usually you log out quite a lot of data.
[2571.70 --> 2573.12] So you have a lot of log statements.
[2573.26 --> 2577.28] And when you have a distributed system, you have distributed log files.
[2577.50 --> 2584.20] So first of all, you need to put that all together into one logging system, which you can have.
[2584.34 --> 2587.16] But then you have a lot of logging statements in there.
[2587.16 --> 2594.86] And it's impossible to really see where problems are or where trends are.
[2595.58 --> 2601.44] And here comes AIOps into play because AIOps can do pattern matching.
[2601.66 --> 2604.16] And there is a ton of tools out there.
[2604.38 --> 2606.90] I don't want to do advertising here.
[2607.50 --> 2608.26] But they are...
[2608.26 --> 2609.04] What do you use?
[2609.18 --> 2609.70] What do you use?
[2609.74 --> 2610.10] That's something...
[2610.10 --> 2614.06] I use, for example, I use quite a lot Dynatrace.
[2614.06 --> 2622.12] And I'm a huge fan of Dynatrace because we have some very difficult projects out there.
[2622.58 --> 2630.60] And we were chasing some performance problems and also some problems where suddenly something didn't work.
[2630.96 --> 2632.24] And we were not finding it.
[2632.24 --> 2636.08] And also with log file analysis, we were not finding it.
[2636.20 --> 2645.76] But by using Dynatrace, Dynatrace was able in minutes to point us to the correct server where the problem was.
[2645.80 --> 2649.32] And it was just a configuration problem on that server.
[2649.72 --> 2653.22] And we were like, whoa, how did that go?
[2653.34 --> 2659.56] And that's quite amazing how good these AIOps systems are already.
[2659.56 --> 2660.16] Okay.
[2661.16 --> 2663.52] Anything other than Dynatrace that you've used and you've liked?
[2663.66 --> 2665.36] I also use Datadog.
[2665.96 --> 2667.24] I like that also.
[2667.74 --> 2669.88] Beside of that, no, I cannot.
[2670.46 --> 2670.68] Okay.
[2670.94 --> 2675.72] So Datadog, we're using it in the same way in that you were shipping logs to Datadog.
[2675.80 --> 2679.90] And then Datadog figured out what was going on in the system based on the logs?
[2680.16 --> 2680.60] Exactly.
[2681.24 --> 2681.54] Okay.
[2682.16 --> 2682.58] Interesting.
[2682.84 --> 2683.04] Okay.
[2683.38 --> 2684.80] We talked about AIOps.
[2684.80 --> 2692.28] Now, in automation, what tools do you find yourself reaching out for when you're automating things?
[2692.66 --> 2697.42] What is in your toolbox or what do you find maybe that your team likes to use?
[2697.80 --> 2697.96] Yeah.
[2698.08 --> 2708.16] What we quite often use when it comes to automation, when it comes to deployment automation, we use quite a lot of Octopus Deploy, of course.
[2708.16 --> 2721.08] And when it comes to CI, CD pipelines, then, of course, we use Jenkins, but also TeamCity, Azure DevOps is also a huge thing.
[2721.32 --> 2724.50] And, of course, GitHub and GitLab.
[2724.74 --> 2724.92] Okay.
[2725.22 --> 2725.46] Okay.
[2726.04 --> 2729.08] And other category was DevSecOps.
[2729.18 --> 2731.14] I think I would call it like supply chain security.
[2731.66 --> 2735.78] What tools do you use for supply chain, for securing the supply chain?
[2735.78 --> 2741.94] We need to understand that there are different aspects of security when we talk about DevSecOps.
[2742.36 --> 2745.10] One thing is the application security.
[2745.42 --> 2754.82] So, when we do continuous integration and our continuous integration server is compiling our source code, we do static code analysis.