WEBVTT
NOTE
duration:"00:50:11.6500000"
language:en-us
NOTE Confidence: 0.802962124347687
00:00:01.240 --> 00:00:13.230
Good afternoon, everyone so you're obviously all the hardcore that database. People aren't seeing guys in a cube doing their session. That's probably the one that's piped out at the moment.
NOTE Confidence: 0.874491631984711
00:00:14.540 --> 00:00:23.830
So you're all here to see doing some smart layouts and Azure. SQL database using a bit of Azure automation, and feeding into some logic apps.
NOTE Confidence: 0.826801061630249
00:00:25.930 --> 00:00:45.790
And my range doesn't seem to be good and switching my slides on so welcome back on here. My name is Martin Kearney. I'm Microsoft data platform MVP have been working around SQL server for the best part of about 20 years now.
NOTE Confidence: 0.878568887710571
00:00:46.830 --> 00:01:06.840
My contact details up there if you want to jump in and follow up in equations or anything afterwards. Feel free to get in touch certainly happy to provide more info. I run things here and if any of you ever get the chance to come down to Australian holiday have a we can come and see our SQL server Saturday event.
NOTE Confidence: 0.881368517875671
00:01:07.720 --> 00:01:25.130
We are the probably the biggest one in the Southern Hemisphere. There are suddenly the The Southeast Asia and Australia areas so that's usually writing about some June time so feel free to come down and have some more fun with those down there.
NOTE Confidence: 0.875119745731354
00:01:27.990 --> 00:01:34.060
So what will run through today? How many of you are actually using SQL DB regular at the moment.
NOTE Confidence: 0.881737470626831
00:01:35.300 --> 00:01:55.310
Mostly that's good OK, so you've got a little bit familiarity to start with us towards there in the platform and obviously some familiarity with the Azure Portal and what you can see in there in terms of how SQL DBS performing so we'll look at taking that and actually triggering off some layouts basically from the port so you know where you can do.
NOTE Confidence: 0.870096147060394
00:01:56.100 --> 00:02:02.130
Set it up through both the portal itself and a little bit through power shell will show you both ways on there.
NOTE Confidence: 0.863658845424652
00:02:03.870 --> 00:02:23.880
And where that will lead into then is using Azure automation, has anybody used Azure Automation for infants. So far, but have you there? They have started on something there. So we'll see how that how powerful that is on creating and an execute and some run books, so that we can actually start to do some some of the tasks that we know.
NOTE Confidence: 0.865224599838257
00:02:24.670 --> 00:02:32.400
SQL DB and more automated fashion. You know, not having to rely on doing things manually and clicking through things in the portal itself.
NOTE Confidence: 0.883710324764252
00:02:34.400 --> 00:02:48.720
Then we'll try and link these 2 up together so we'll start seeing where we can take out of layouts and have them kick off or run book automatically so then we've got that there. We don't have to be involved for some of the critical aspects that can happen with our databases.
NOTE Confidence: 0.875392436981201
00:02:50.440 --> 00:03:08.890
And then we'll do the fun stuff World Hook that on Interlogic app as well and sure you wear over their the power of logic apps. You can start to do pretty much anything you want throughout your environment and react to your layouts and deal with them and a more automated minor in a more complex minor more thorough manner as well.
NOTE Confidence: 0.855816066265106
00:03:12.200 --> 00:03:32.210
So when we look at a layouts in the Azure portal. One of things and I'll drop into with a little bit more detail and a little bit further on, but those those 2 methods of alerting at the moment. One of them is based the point. It's been there since. The adult with a with Azure. It's the classic a layout.
NOTE Confidence: 0.834042727947235
00:03:33.010 --> 00:03:35.830
Is a different framework there?
NOTE Confidence: 0.89415317773819
00:03:36.890 --> 00:03:56.900
But it still exposes it but just to be aware that although I'm going to cover some stuff with that today. It's mark for the application. It will be going middle of this year. So the alternative layouting framework, which will cover about with it as well. But that would be the way you look at going forward. What I've done is with some of the demos today.
NOTE Confidence: 0.872746229171753
00:03:57.690 --> 00:04:17.700
Just because it's a little bit quicker to get things triggered off so it's really just for simplicity, just to show things through there, but in terms of what we do later on. We can either have it going from metrical events that are happening within our platform, so for example, RDTU consumption hits a certain point in certain.
NOTE Confidence: 0.865415275096893
00:04:18.510 --> 00:04:38.520
We can have no layout, triggering off based upon that the other bits based point just generalize your activities so for example. If somebody creates a new database and our logical server in Azure. Let's get a layout and you know trigger something else off if we need too or just informed people for example, is it set up properly for a bill back purposes.
NOTE Confidence: 0.887294590473175
00:04:39.310 --> 00:04:45.260
So it might just want to know about these things happening and we can use a layout together that information as well.
NOTE Confidence: 0.869053363800049
00:04:48.500 --> 00:05:08.510
The way we react or layers is quite configurable. There's an awful lot of stuff that we can throw into their the basic? Where is just to be send an email to the administrator or to anybody that's in that particular Azure role. So we can be customized was to who gets that email and notification we can be specifically can you know?
NOTE Confidence: 0.848751723766327
00:05:09.300 --> 00:05:18.840
And unattended mailbox that's outside of the Azure account. We can have it trigger off to that as well. So there's good flexibility as to where we can send the the notifications off to.
NOTE Confidence: 0.885570108890533
00:05:20.230 --> 00:05:34.080
But it also gives us the power of using webhooks so from that, we do have that ability to hook into anything that will accept a webhook and start to trigger things off in there or seeing that additional information into those other systems.
NOTE Confidence: 0.83076024055481
00:05:37.620 --> 00:05:44.400
So as I mentioned some details date about when the classic alerts are going to disappear.
NOTE Confidence: 0.867967367172241
00:05:45.900 --> 00:05:47.730
Within SQL DB at the moment.
NOTE Confidence: 0.867788016796112
00:05:48.860 --> 00:06:08.870
Is probably worthwhile still persist in with them for a little bit longer really just for the metric tape layouts from the classical S is so much easier to do it's a bit simpler to get things up there that often running. I'd recommend you still go with that just know, but start looking into the new metrics.
NOTE Confidence: 0.875558912754059
00:06:09.660 --> 00:06:29.670
Is the way it's exposed in the portal it looks as though there still something that's not quite being fed through there's a little bit of a disjoint between the documentation of what you actually see in the portal so again just trying to follow things through have a look at good. Sam Peyton things out. This way for just know and then look to adapt.
NOTE Confidence: 0.86315643787384
00:06:30.460 --> 00:06:36.140
Within the next few months as we get closer to the classic lyrics being cut off.
NOTE Confidence: 0.499291777610779
00:06:42.610 --> 00:06:43.130
So.
NOTE Confidence: 0.886829853057861
00:06:44.450 --> 00:07:00.410
We got a couple of ways, we can create that layout. You know, we can start off looking at it through the portal or we can consider power shell is A is a good framework to do that. So let's have a look and jump in and just get some familiarity with things first of all.
NOTE Confidence: 0.857855498790741
00:07:01.610 --> 00:07:03.900
And let me flip that over.
NOTE Confidence: 0.885613203048706
00:07:09.970 --> 00:07:17.560
All right, so the Azure Portal that everybody's familiar with where I want to drop into first of all is into my database.
NOTE Confidence: 0.846635282039642
00:07:21.130 --> 00:07:28.910
And don't hit under the monitoring's where we've got the ability to set up the DVD sellouts, so the classical outs at the moment.
NOTE Confidence: 0.900045931339264
00:07:30.020 --> 00:07:50.030
We can quite easily come in at something which is based for example, on the the activity log. So we can start to see any of the configuration changes and things around. Our database can be picked up here. So we can start to look at the various different configuration types, we have there on uh.
NOTE Confidence: 0.525012195110321
00:07:52.180 --> 00:07:53.310
Jump back.
NOTE Confidence: 0.914657533168793
00:07:55.940 --> 00:07:56.940
The metrics.
NOTE Confidence: 0.882400214672089
00:07:59.140 --> 00:08:02.810
We start to see the various things that we can look at on here.
NOTE Confidence: 0.887012183666229
00:08:05.850 --> 00:08:10.270
For example, if we're going to consider something like a DTA usage.
NOTE Confidence: 0.87413090467453
00:08:11.210 --> 00:08:31.220
We can see you just make it that way. So our charts. There are going to be the things that we're going to start basing our metrical layouts on as well. This sort of information. We can set up that gets passed out into log. Analytics within Azure. And then we have the power of the query language upon their to start pulling out the actual.
NOTE Confidence: 0.886204957962036
00:08:32.090 --> 00:08:36.770
That we're interested in So what I'm going to do is.
NOTE Confidence: 0.876949906349182
00:08:38.560 --> 00:08:41.640
Start through just the setup of a couple of laps.
NOTE Confidence: 0.843863308429718
00:08:46.670 --> 00:08:50.770
So you setup where I'm sending things too, and connecting up.
NOTE Confidence: 0.843120932579041
00:08:52.950 --> 00:08:54.070
To measure subscription.
NOTE Confidence: 0.890252947807312
00:08:57.560 --> 00:09:15.820
So the first thing I need for the new matrix is to get our log. Analytics workspace, we actually need somewhere where it's it's going to start dumping this information out on a constant basis and expose it to to be able to then query and actually find the conditions where we want to trigger overlaps so will do that first of all.
NOTE Confidence: 0.874403893947601
00:09:18.920 --> 00:09:22.370
The other concept within that is this bit with an action group.
NOTE Confidence: 0.903559923171997
00:09:23.740 --> 00:09:43.750
The other nice bit about the new format of their the metrical layouts is that we can start to reuse. A lot of the components. So if we've got a standard way of doing North notifications for example, if there's a certain group of people that need to be emailed or SMS or things like that, we can package that up into an action group and reuse that across.
NOTE Confidence: 0.779447138309479
00:09:44.540 --> 00:09:49.270
So it's just a simple way of packaging things up together there.
NOTE Confidence: 0.918025314807892
00:09:56.210 --> 00:09:59.770
So one is not still think it's running.
NOTE Confidence: 0.838944375514984
00:10:08.150 --> 00:10:11.140
Pretty sure context to set OK.
NOTE Confidence: 0.827037215232849
00:10:15.830 --> 00:10:20.310
Hopefully it's not going to be network gremlins out in impacting everything there, we go.
NOTE Confidence: 0.877609550952911
00:10:38.900 --> 00:10:41.900
Alright let's hopefully that has.
NOTE Confidence: 0.842942655086517
00:10:43.380 --> 00:10:45.660
Set it up hold up alright.
NOTE Confidence: 0.7826247215271
00:10:50.680 --> 00:10:52.760
OK so while that's running.
NOTE Confidence: 0.863561153411865
00:10:56.230 --> 00:11:16.240
Within this they are the next best chords. I've gotten here it should then configure the database to see. I'm going to start pumping out my matrix information into the log. Analytics workspace, there seems to be a bug in it. I'm tracking tight track it down as to what's going wrong, but fake?
NOTE Confidence: 0.879990339279175
00:11:17.030 --> 00:11:23.670
Doesn't properly enable it so I'm just going to bypass that and come back in and do that through the portal.
NOTE Confidence: 0.861697316169739
00:11:30.850 --> 00:11:37.930
So this is where I would set that up and what I want to do is to say. I'm going to save my Darent Diagnostic Center Log Analytics.
NOTE Confidence: 0.884989738464355
00:11:39.140 --> 00:11:59.150
I've got it marked into my workspace there and I want to make sure that it's all matrix is configured at the bottom and that's about this thing going to see all of the performance information of my database. So things like the detour consumption. The the size. All that sort of stuff that will then be pushed out into the Log Analytics.
NOTE Confidence: 0.886107802391052
00:12:00.130 --> 00:12:20.140
And allow it to be queried so that we can generate our conditions from there. The other bit around the the other side is where we can start to look at some of the more activity based information and include that to be sent out as well. If we want to. But at the moment. We're just going to leave. It just with the the metrics being sent out into our log analytics workspace.
NOTE Confidence: 0.871798276901245
00:12:20.930 --> 00:12:24.340
Looks as though it's pick, things up correctly there.
NOTE Confidence: 0.929163992404938
00:12:36.330 --> 00:12:45.500
So it seems to be running very, very slowly at the moment I don't know if that's my network, connection or whether it's just not a great day for Azure.
NOTE Confidence: 0.848078489303589
00:12:49.160 --> 00:12:52.650
OK will jump on to the next player anyway from here.
NOTE Confidence: 0.759927809238434
00:13:04.370 --> 00:13:05.400
Is that was still running?
NOTE Confidence: 0.855095982551575
00:13:09.610 --> 00:13:13.180
There we go that's probably far enough no to get through it yet cool.
NOTE Confidence: 0.864840805530548
00:13:21.730 --> 00:13:24.590
So I want to come into my my workspace now.
NOTE Confidence: 0.835777223110199
00:13:27.620 --> 00:13:31.370
And I know look at generating some layouts from there, the monitoring that's going on in here.
NOTE Confidence: 0.91528332233429
00:13:53.960 --> 00:14:09.160
It does actually need to have some of that information already in the log. Analytics workspace, or will tell you that it's not finding anything. Maybe you get something wrong with your your query there. So I'm just going to start off a little bit of a workload just to generate something going through.
NOTE Confidence: 0.87173730134964
00:14:12.500 --> 00:14:32.510
So what I want to look at is doing a custom log search. So this is the way that we get our matrix information. Now the other one will start with you get the option. They're picking out particular event. So if you want to look for a specific event occuring there's a nice way of finding that through there, but anything, it's coming just from the general metric side of things we need.
NOTE Confidence: 0.729762375354767
00:14:33.300 --> 00:14:35.740
Prepared a query to look at that.
NOTE Confidence: 0.840066015720367
00:14:37.600 --> 00:14:38.100
I'm going to.
NOTE Confidence: 0.868638694286346
00:14:39.500 --> 00:14:41.810
Drag my query from here.
NOTE Confidence: 0.912980496883392
00:14:43.940 --> 00:14:53.210
So it's worth while also having a look at the query language for log analytics, which is consistent across everything that you would do within that that whole workspace.
NOTE Confidence: 0.895512819290161
00:14:55.890 --> 00:15:10.300
And it's a fairly fairly simple sort of syntax approach, it starts off as your metrics is going to be our kind of entity area that we're looking at from that, we're going to order it by time.
NOTE Confidence: 0.861558139324188
00:15:11.620 --> 00:15:31.630
We cannot in a couple of where clauses so again, you get familiarity from U SQL syntax to what we're trying to do here. So we're looking at the layouts of the messages that have come in from the Microsoft dot SQL provider within that that is all sorts of different levels of messages were filtering that down too.
NOTE Confidence: 0.736588954925537
00:15:32.420 --> 00:15:33.120
This is level.
NOTE Confidence: 0.805863261222839
00:15:34.380 --> 00:15:37.270
We look at our metric of being RDTU consumption.
NOTE Confidence: 0.868493378162384
00:15:39.030 --> 00:15:59.040
And then I want to look at you look Viagra Gation over. I want to see when things are happening over a period of time, so on this one. I'm averaging the DTO consumption over 5 minute periods. Getting the average of that and then filtering again on that one and seeing.
NOTE Confidence: 0.877856433391571
00:15:59.830 --> 00:16:15.750
Want to get something coming out or any rules return from this query whenever that is consistently over 80%. So if my average over the last 5 minutes for DTE consumption that database has been 80% or higher. Then I'm going to get something returned and be able to trigger on a layup from that.
NOTE Confidence: 0.88960212469101
00:16:17.580 --> 00:16:35.920
The bit there when I can project it. That means I can get these other pieces of information and be consistent with what I expose into some of the downstream stuff. So where I want to start looking at for example, that pay Lord being triggered into Webhook, then I need to have that information exposed out of the source data as well.
NOTE Confidence: 0.883249402046204
00:16:37.230 --> 00:16:38.910
So we'll see.
NOTE Confidence: 0.872210919857025
00:16:43.050 --> 00:17:03.060
As I said, You know it's giving me an error that moment because it hasn't generated enough data through into the workspace. So we can come back to that and a little bit and trigger that often make sure everything else is put through their butt fake believe what I've done on this one is because I've already aggregated up and looking back over my 5 minute piece.
NOTE Confidence: 0.911525249481201
00:17:04.060 --> 00:17:18.150
I want to get in a layout whatever that has happened at anytime in there, so I'm not looking at how many individual events have come back in that. Period. I'm just saying have I actually returned an average over 80% at all?
NOTE Confidence: 0.89011162519455
00:17:19.510 --> 00:17:28.110
So, in that case, I want to set my threshold to zero so if I've come back with anything greater than zero. That means my threshold was breached and I want to trigger that event.
NOTE Confidence: 0.923286199569702
00:17:29.780 --> 00:17:32.650
So we're going to look at that over every 5 minutes.
NOTE Confidence: 0.870953679084778
00:17:33.600 --> 00:17:53.610
Well, they run it every 5 minutes. I'm going to look at rolling fragmented pedia that's affected with a bit of the bottom says on there, so at the moment I can't actually save that and configure it until it's passed through properly into the workspace, but that's effectively high we would generate that there. Now, the where clause then there gives us so much more flexibility in this.
NOTE Confidence: 0.880644083023071
00:17:54.400 --> 00:18:04.990
I can now do this as a single. A layout across all of my SQL databases. So I might want to go OK, bringing the information and for everything.
NOTE Confidence: 0.879351258277893
00:18:06.080 --> 00:18:26.090
I might only want to see for a specific one. I could add another where clause and I actually specify the database name or I can leave it like this and go 10 layout is no covering my entire suite of SQL D BS. I don't need to go and configure things individually for them. It's all done in one place you got that nice simplification coming.
NOTE Confidence: 0.786575376987457
00:18:26.880 --> 00:18:28.190
Collapse as well that way.
NOTE Confidence: 0.404444873332977
00:18:32.120 --> 00:18:33.580
OK.
NOTE Confidence: 0.588480174541473
00:18:35.500 --> 00:18:38.000
Coming back.
NOTE Confidence: 0.889792799949646
00:18:55.880 --> 00:19:01.590
The other way, I can do this and see if it's picked anything else up it might just be that's not.
NOTE Confidence: 0.859832346439362
00:19:04.860 --> 00:19:05.900
Fishing it hard enough.
NOTE Confidence: 0.58358246088028
00:19:13.010 --> 00:19:13.450
OK.
NOTE Confidence: 0.834028244018555
00:19:15.480 --> 00:19:26.710
We'll come back to that will kick it into the next this station. We can back to demos will run through the rest of it from there 'cause, we should have something generated by that point.
NOTE Confidence: 0.820497095584869
00:19:48.100 --> 00:19:58.350
All right, so we've got our layout set up the other bit will look at it from that is just how simply is to create the classic hilarious as well. When we jump back in the next demo.
NOTE Confidence: 0.823721051216125
00:19:59.340 --> 00:20:01.870
Our next background is Azure automation.
NOTE Confidence: 0.899938762187958
00:20:03.120 --> 00:20:18.450
So it's a service within the whole of the Azure platform, and effectively it can interact with anything. You've got there, so anyway. You want to start working in unattended bits of activities, Azure Automation is that your your way to go.
NOTE Confidence: 0.88203638792038
00:20:20.350 --> 00:20:40.360
Some of the stuff that we can do you know we cannot process automation so we can start to see it scheduled times? Let's do all these various steps across things and RI Azure infrastructure. So we might want to you know run something which gathers an inventory of all the SQL databases. We've got and passes that are in somewhere else you know that sort of.
NOTE Confidence: 0.912388324737549
00:20:43.010 --> 00:20:57.000
We can configure things we can use it. For example, to identify systems that we should shut down overnight. For example, you know, some of those nice ways of saving money. So if your if your business only runs 9 till 5.
NOTE Confidence: 0.860516309738159
00:20:58.390 --> 00:21:18.400
Why not? Just you know have something shared which shuts down or your VMS in Azure after 5 o'clock at night and then start them all up again, the next day. Save you a whole heap of cost by not running things over that period in time. So you know, some nice ways of managing it across that it actually has the ability to Hook back in and do some on premises stuff as well.
NOTE Confidence: 0.896410048007965
00:21:19.190 --> 00:21:33.440
That's being way beyond what we're going to be covering for this at the moment, so really what we're interested in is how can we use this to help manage our SQL databases and then also how can we trigger that off in some way to to make it more responsive?
NOTE Confidence: 0.88055145740509
00:21:37.100 --> 00:21:56.630
So Azure automation, fatal is just a way of of running scripts in the in the cloud. So it's based appoint mostly power. Shell, however, that is the opportunity. No to have python scripts in there as well. So you can then interact with the whole sort of CI type approach to that.
NOTE Confidence: 0.822808921337128
00:21:57.610 --> 00:22:09.630
Designing your run books can either be done in a gui manner. So it gives you that better. Just linking fits together bits a process or you can have it just as a script itself.
NOTE Confidence: 0.852878987789154
00:22:12.110 --> 00:22:25.860
You might do your development outside of Azure. So you might do. It just in the power shell ID workout. What your script? Is there a nice way is then you can just import that directly into your run book and it's all configured and ready to go from that point.
NOTE Confidence: 0.893232882022858
00:22:27.000 --> 00:22:47.010
And there's also a Runbook Gallery. There's a lot of standard scripts that are already created so again. You don't bother going reinventing. The wheel when you don't have to have a look at the Runbook Gallery. Find out there's anything there. That's doing what you actually need to be able to do so for example, I'm pretty sure it'll be one which will be able to identify your VMS to shut.
NOTE Confidence: 0.180002838373184
00:22:47.800 --> 00:22:48.380
So.
NOTE Confidence: 0.872915506362915
00:22:49.520 --> 00:23:09.530
The important thing to have with it, though, is your run eyes account now effectively what that does is sets up a service principle in Azure AD, which has got the permissions to go out and actually interact with all your Azure services. So it's like having that the main admin and unattended account.
NOTE Confidence: 0.880573391914368
00:23:10.320 --> 00:23:13.410
People to go out and do all the The Tasks that needed to be done.
NOTE Confidence: 0.884195983409882
00:23:18.000 --> 00:23:38.010
It's a couple things really just about the different style of workbooks. The graphical ones gives you that nice of step by step, visual of what happens so you can go through and say, I need to do steppe before step. BI can have conditional floors between them. So it kind of like you know, an SSIS package so look and feel.
NOTE Confidence: 0.554212212562561
00:23:38.800 --> 00:23:39.520
And it that way.
NOTE Confidence: 0.836323738098145
00:23:42.140 --> 00:24:02.150
With the graphical design format, though if you go through that. Yes, you can export its text doing your perhaps put it in source control, but you can't then into outside of that. You can only edit that by pulling it back into the gui and to the degree edge stuff and and everything.
NOTE Confidence: 0.734128534793854
00:24:02.940 --> 00:24:11.770
So you kind of locking yourself in to that approach if you go in there.
NOTE Confidence: 0.838668346405029
00:24:13.010 --> 00:24:24.910
You've got the nice part of being able to your call additional run books from a single run books that whole sort of parent child format. So you do get that re use of some of your run books across various other ones.
NOTE Confidence: 0.791167616844177
00:24:29.090 --> 00:24:30.150
For the text ones.
NOTE Confidence: 0.858491063117981
00:24:31.410 --> 00:24:40.560
Effectively, just power shell scripts, so you can run that from anywhere. You want to run Powershell. You can have it sitting as a file and just call it through power shell on your own machine.
NOTE Confidence: 0.902493536472321
00:24:41.580 --> 00:24:43.150
So easy enough to put in there.
NOTE Confidence: 0.890999913215637
00:24:44.100 --> 00:25:02.110
You do see obviously all the code is it going through design. All that in a step by step basis. But you do then have to make sure that you build in all your own conditions to make sure that what you're doing is actually going to do the right steps so if you've got some conditional logic. You obviously have to you write that in and handle it yourself.
NOTE Confidence: 0.850975811481476
00:25:06.320 --> 00:25:26.330
So once we've actually created a run books. There's a couple of ways that we can then call those so we can actually just go straight into the portal gorthaur automation account get to the Runbook. We want click run pass in any parameters specifically they might need and that will go off and do that. It also includes an invoke.
NOTE Confidence: 0.868993163108826
00:25:27.120 --> 00:25:33.410
Decide to say, yeah, we're going to run this at 6 o'clock every night and do our shot down over VMS for example.
NOTE Confidence: 0.851423919200897
00:25:35.370 --> 00:25:55.380
You can also call them programmatically so either through power shell, the CLI and just say start that automation runbook specified. What is basically any parameters that need to be passed in but the nice but from that is that we can set them off in response to webhook so that's where we're starting to get our linkage back in.
NOTE Confidence: 0.80226868391037
00:25:56.170 --> 00:26:16.180
Remember, when we looked at the layout definition to start with that was the ability to tag into a webhook as well. Like balancing that would be on the classical layouts that will show you that, but so effective. We've gotten that we have just linking these 2 bits together and going. I have no gotta condition happening.
NOTE Confidence: 0.801438510417938
00:26:16.970 --> 00:26:23.930
I have a run book, which handles that condition. Let me link the 2 so that when it happens, I can trigger it off.
NOTE Confidence: 0.873287200927734
00:26:25.470 --> 00:26:45.480
So we can then start to see some of the 9 stuff week. We can think about it, so things like our performance levels. If we do get this condition, where it's been running at 1890 percent for the last 5 minutes solidly well let's make use of the flexibility and the pass system and go away. It's just dial up the DT use. Give me a more power.
NOTE Confidence: 0.928689897060394
00:26:46.520 --> 00:26:47.780
Until things calm down.
NOTE Confidence: 0.871782720088959
00:26:48.850 --> 00:27:08.860
The nice because I can then also have another it going. The other way, there if it drops below a particular threshold. From time period. Dial it back down again. So this is my automatic handling of dynamic responses to the Lord. That's on my system when it's in heavy Lord. I'll dial it up. I'll pay a bit more, but I'll get the perform.
NOTE Confidence: 0.817308247089386
00:27:09.650 --> 00:27:15.620
Is it going to be happy and then? When it was quiet again? Let me just really just smack down just to save myself, some costs.
NOTE Confidence: 0.888356924057007
00:27:21.800 --> 00:27:28.690
So nice but both the web perk implementation is that everything that we need comes through within their the HTTP definition for that.
NOTE Confidence: 0.897588670253754
00:27:29.650 --> 00:27:49.660
So really we go and we set things up. We get that copied from our automation run book. We just need to piss that back into our source and that's all we need to do all of our authentication is contained within that all the parameters that we need have already been defined and pass through as long as that is exposed in what's the other another layout.
NOTE Confidence: 0.888388633728027
00:27:50.450 --> 00:27:52.050
Oh, good everything will just work.
NOTE Confidence: 0.879473924636841
00:27:58.590 --> 00:28:09.430
The next step on that is when we take things up till logic app and I'm just going to go through. I'm going to finish off in a couple of slides and then we'll go in and actually get this working end to end so that we can see how the day kicks off.
NOTE Confidence: 0.830879271030426
00:28:10.860 --> 00:28:13.660
So the next but now it used to be that.
NOTE Confidence: 0.869168698787689
00:28:16.610 --> 00:28:36.620
The scope of our of what we can get the logic app. So it's it's kind of like you know best talk in the cloud. If you if you use best talking to pastor being exposed to it, so it gives us that huge range of different connectors and processes that we could we can make yourself. So we can then define our floor through that as well. We can say How do I want to take this source in where?
NOTE Confidence: 0.840008735656738
00:28:37.420 --> 00:28:57.430
I want to react to that I may get a response back from the other systems that I'm interfacing with so for example, you might be able to do is build a complex workflow which says let me take an all out. See it's let's say it's a performance one RDT use. Let me send off a message.
NOTE Confidence: 0.882569909095764
00:28:58.220 --> 00:29:18.230
I ticket management system and say raise an issue that this database is seeing performance issues. I can then go off and go right, I've got the response back from that with my ticket number for example. Let me hold that in available. Let me go off increase my DT you limit if that happens successfully gray.
NOTE Confidence: 0.871361970901489
00:29:19.020 --> 00:29:39.030
And settle down, I can now go and post. Another message back into my case, and say, I've no resolve that issue. So it's there. It's been fixed. But you haven't lost sight of important. Lee you don't lose that information that you've you've had the issue your case system your layout system. There can still give you the man.
NOTE Confidence: 0.913694977760315
00:29:39.820 --> 00:29:54.050
Times that particular event happens. Everything is good you know you got those statistics. You can then see overtime. They need to go back and look at this because it's happening on a frequent basis. Maybe I should just leave this at the higher level, ongoing for this one.
NOTE Confidence: 0.879187762737274
00:29:55.060 --> 00:29:57.010
It's all sorts of nice stuff you can do on there.
NOTE Confidence: 0.846084654331207
00:29:58.880 --> 00:30:18.890
The fund better was going to have a play with, but didn't quite get round to in time for this was then looking at how I can interface so to other systems and particularly may be looking at something like home automation. You could even set something up to go. Let me flash a light bulb whenever I get performance on that so.
NOTE Confidence: 0.876317977905273
00:30:18.910 --> 00:30:38.920
Something that can you know this sort of endless approaches that you can think of from this as well. You might have you know a lay in your your office area that goes? Let me flash the rage whenever something's happened go off and have a look at it. So you can have fun with it around that way as well, but you know it just demonstrating the.
NOTE Confidence: 0.802869200706482
00:30:39.710 --> 00:30:42.650
Of what you can do is is fairly limitless from there.
NOTE Confidence: 0.892678797245026
00:30:45.180 --> 00:30:49.570
So let's go back, then, and let's see if.
NOTE Confidence: 0.916221618652344
00:30:51.090 --> 00:30:54.360
Everything has finished off and the portal.
NOTE Confidence: 0.945591628551483
00:31:08.470 --> 00:31:10.350
That's not looking good.
NOTE Confidence: 0.829014420509338
00:31:41.210 --> 00:31:44.320
Run it should definitely had some load on its?
NOTE Confidence: 0.778060495853424
00:32:01.850 --> 00:32:04.670
OK demo bugs on that one so let's.
NOTE Confidence: 0.101950600743294
00:32:16.340 --> 00:32:20.280
is?
NOTE Confidence: 0.826832294464111
00:32:28.240 --> 00:32:30.450
Let's build this out as a classic alert.
NOTE Confidence: 0.877794325351715
00:32:47.130 --> 00:33:04.210
So the same one will based on RDT percentage interesting that issue and there has been something happening. So I'm not sure why the other layouts. They want to pick it up yet, so let's see what we been hitting is let's make that.
NOTE Confidence: 0.855784118175507
00:33:07.070 --> 00:33:09.880
40% in just to make sure that we trigger things off easily.
NOTE Confidence: 0.798703134059906
00:33:14.840 --> 00:33:18.180
Get our notification.
NOTE Confidence: 0.870740711688995
00:33:22.000 --> 00:33:29.970
And will trigger that off so we've now got that that real created as well. So there's our our classic one which will fire off from there as well.
NOTE Confidence: 0.254124671220779
00:33:36.670 --> 00:33:37.470
OK.
NOTE Confidence: 0.857743263244629
00:33:39.480 --> 00:33:42.610
So next bit let's go through and.
NOTE Confidence: 0.879509627819061
00:33:49.270 --> 00:33:50.690
Look at our automation account.
NOTE Confidence: 0.880052149295807
00:34:25.220 --> 00:34:28.270
So that's setting up my basically account to start with.
NOTE Confidence: 0.875368416309357
00:34:33.500 --> 00:34:49.990
Make sure that completes all right now, the The Corbett around that is just making sure doing it. That way that setting up my run as account. So we've got that already preconfigured within the automation account so that when I start tired there. They run books and then it will just work. It would just have the access it needs.
NOTE Confidence: 0.884946346282959
00:34:52.390 --> 00:35:07.830
So we created the automation account is no doing those runners accounts, so while it's doing that I can come back on to this one. I'm just going to create the runbook through Powershell. So I'm just saying some variables here first of all.
NOTE Confidence: 0.906079888343811
00:35:10.860 --> 00:35:16.630
And what I'm doing is I'm importing it from a file already got so I've already created the scripts that I need for this one.
NOTE Confidence: 0.817600905895233
00:35:18.010 --> 00:35:21.560
Soul import that and published that to my automation account.
NOTE Confidence: 0.873639702796936
00:35:42.690 --> 00:35:45.720
So there's my run book being created there.
NOTE Confidence: 0.870530962944031
00:35:46.920 --> 00:36:06.260
I'm just saying If I just come in and have a look at it, you'll see. It is just some reasonably straightforward power. Shell, the important bits around it are the couple of lines here where we get the the coin takes first of all, so making sure that's the right subscription that it's it's running in and then also or
NOTE Confidence: 0.869758069515228
00:36:07.630 --> 00:36:08.680
Connection.
NOTE Confidence: 0.886632859706879
00:36:09.650 --> 00:36:19.340
Me using the Azure runners, connection, so effectively, saying that we're going to run as a service principle rather than any particular user so it's nice and straight forward from there.
NOTE Confidence: 0.874314725399017
00:36:28.350 --> 00:36:32.170
So to show it, running I'm just going to kick it off from from here as well.
NOTE Confidence: 0.874782145023346
00:36:34.220 --> 00:36:54.230
So I'm just going to grab it the same resource group, the same 7 name that we've already created things into I'm going to run off my adventureworks database? What I'm going to do is get the current tier level with my database. I'm going to set up those parameters to call my runbooks. I'm going to pass it in because it's been written in a flexible way.
NOTE Confidence: 0.866920590400696
00:36:55.020 --> 00:36:58.020
Any Resource Group Server database combination.
NOTE Confidence: 0.833128809928894
00:36:59.040 --> 00:37:07.030
Will kick that off wait for it to finish and then the end of it will confirm that it's actually change the tear on that.
NOTE Confidence: 0.87177050113678
00:37:12.000 --> 00:37:21.890
Basically have to start with it should take about a minute to run through on this and come back and give us the updated version from there.
NOTE Confidence: 0.831433773040771
00:37:27.880 --> 00:37:29.250
While that's on the door.
NOTE Confidence: 0.90932422876358
00:37:31.960 --> 00:37:33.950
Let's have a look at the logic apps.
NOTE Confidence: 0.860016703605652
00:38:04.230 --> 00:38:06.700
So let me grab my name for that.
NOTE Confidence: 0.311965346336365
00:38:16.200 --> 00:38:17.910
One.
NOTE Confidence: 0.880922377109528
00:38:20.800 --> 00:38:24.890
That one and let's just make sure we create that locally will keep it.
NOTE Confidence: 0.832710981369019
00:38:35.750 --> 00:38:55.760
There we go that's so that's finished through on that one so there was seen it's triggered offer run book. It's going through phone dialing it always changing things up and away. I've just I've written that was just a flip flop. So I can reuse the same run book and send it. The other way you know, basically saying if it's no running in Seattle. Dial it back down to basic tier on.
NOTE Confidence: 0.838967084884644
00:38:56.590 --> 00:39:06.140
So fairly straightforward nothing too fancy out of that, but just showing that how users to trigger that run book and have it actually deal with that for us.
NOTE Confidence: 0.843138813972473
00:39:07.210 --> 00:39:09.030
Going to my logic app.
NOTE Confidence: 0.893008768558502
00:39:24.080 --> 00:39:44.090
So I'm going to start off with just a blank one here, but there's a number of templates. You can start with the other already setting up there. The particular connections that you want to use what I'm going to do is for this one is generally a connection it to slack. So I'm going to see if I can trigger my layout and have that post into a slack channel with a message of what's happened.
NOTE Confidence: 0.842937767505646
00:39:54.550 --> 00:39:59.500
And there are so faithfully just giving it the authorization to be able to link through.
NOTE Confidence: 0.84037446975708
00:40:00.720 --> 00:40:02.020
Hello that access.
NOTE Confidence: 0.880692064762115
00:40:06.090 --> 00:40:11.520
Cool. So why they want to do here is just do a little bit of a shortcut.
NOTE Confidence: 0.881314814090729
00:40:14.960 --> 00:40:23.410
So I'm going to take the cord out from there for what it's actually trying to do, I just want to reuse that connection ID?
NOTE Confidence: 0.91112345457077
00:40:27.240 --> 00:40:28.890
I have a
NOTE Confidence: 0.799493253231049
00:40:30.310 --> 00:40:31.050
That one.
NOTE Confidence: 0.882403135299683
00:40:44.840 --> 00:40:47.850
So we just make some re use of that connection.
NOTE Confidence: 0.759400427341461
00:40:51.500 --> 00:40:53.940
I just clean up this first bit again.
NOTE Confidence: 0.879935026168823
00:41:04.700 --> 00:41:14.570
Cool. So now, what I'm doing is going my input is going to be my HTTP request, which is coming from the payload of my allowed filing.
NOTE Confidence: 0.867695152759552
00:41:16.130 --> 00:41:36.140
I'm doing a little bit here just for the particular message of God, just to show that we can actually go out and interface with other bits. But what I'm getting is a link back to the alert page within the Azure portal, sending that out to just get shortend URL, which I'll then including the message that's posted in slide so it.
NOTE Confidence: 0.869664013385773
00:41:36.930 --> 00:41:56.940
Of having this huge big URL coming through where the the link has back to there. It's just a nice little bit of function just to to make it a little bit more friendly so that's all that. One is doing and then we're coming out to my slack channel and I have the various parameters. I've been exposed through there, so the things I've come in through the payload property.
NOTE Confidence: 0.884750723838806
00:41:57.730 --> 00:42:16.470
So so I can start to get things like the the resource name that was involved. The name of the database what the status of the layout was my ID, which is come back from my HTTP call out to shorten the URL so it's just nice and straight forward from there.
NOTE Confidence: 0.915393233299255
00:42:23.580 --> 00:42:29.510
I just need to get rid of this one again. I forgot that I actually had a second one in there.
NOTE Confidence: 0.535538196563721
00:42:33.230 --> 00:42:33.630
Cool.
NOTE Confidence: 0.854614675045013
00:42:38.870 --> 00:42:41.560
So if I come back now to my layout.
NOTE Confidence: 0.717491388320923
00:42:43.080 --> 00:42:44.460
So back to media at this.
NOTE Confidence: 0.872504830360413
00:42:56.570 --> 00:43:03.580
I just got a nice little link here. They just automatically takes me through and says let me call a logic app.
NOTE Confidence: 0.906727075576782
00:43:06.530 --> 00:43:08.080
Which we know how from there?
NOTE Confidence: 0.845439255237579
00:43:09.270 --> 00:43:10.380
I saved that.
NOTE Confidence: 0.800857305526733
00:43:14.140 --> 00:43:15.080
Again, just to.
NOTE Confidence: 0.918645560741425
00:43:16.520 --> 00:43:19.180
Makes things tick through a little bit quicker.
NOTE Confidence: 0.748531401157379
00:43:22.410 --> 00:43:23.580
Let's buy that down.
NOTE Confidence: 0.837325155735016
00:43:27.560 --> 00:43:28.680
So if I know.
NOTE Confidence: 0.882235765457153
00:43:30.950 --> 00:43:41.030
Fill up my slack channel make sure I'm still need to restart my lords because I lost my connection when it bumped up to the higher tier.
NOTE Confidence: 0.88878870010376
00:43:47.560 --> 00:43:59.760
So we've got that running now we've got some Lord. It's just going to take some time to get that actual trigger through and fired off the logic app. So I'll leave that up is there any questions while we're waiting for that to come up?
NOTE Confidence: 0.826677083969116
00:44:10.200 --> 00:44:30.210
So question how managed as the logic app cord so from that, as you saw that we were able to just show the JSON version of it as well. So the full details in there. Yes, you could take that out. Save it elsewhere, and and have that templated and store that and.
NOTE Confidence: 0.843386590480804
00:44:31.000 --> 00:44:50.920
Have that managed in there, obviously within the Azure Portal itself. You're looking just your bag controls the oldest who's got access to do various things there. So, your role based think insecurity. This thing if you do your versioning and doing a deployment through arm templates. Then you can have it that way of of refreshing it through there.
NOTE Confidence: 0.355441480875015
00:44:52.860 --> 00:44:53.290
Andre.
NOTE Confidence: 0.868661642074585
00:45:14.600 --> 00:45:34.610
So I just I some comedy Outback why the might not be fighting potentially on it being one minute. Basically, you know checks through on their the Lord and whether that was no averaging over that the classical out was fighting with the Lord. So we've got that one that has had triggered so it's probably not that.
NOTE Confidence: 0.873333811759949
00:45:35.400 --> 00:45:55.410
Yeah, this is something I can you need to do just a little bit of troubleshooting to find out what it is, but the fact that we are getting our layout triggered off just means there's something not coming through. It looks as all the linkage through into log Analytics. Perhaps wasn't enabled properly as the bed there because the query wasn't returning anything for me on the the even to find.
NOTE Confidence: 0.955071270465851
00:45:56.200 --> 00:46:04.190
Unfortunately.
NOTE Confidence: 0.879097878932953
00:46:06.560 --> 00:46:10.450
So with fingers crossed this is actually going to trigger off before we finish up yes.
NOTE Confidence: 0.711236894130707
00:46:22.690 --> 00:46:25.000
So I'm not quite catching.
NOTE Confidence: 0.875472187995911
00:46:31.570 --> 00:46:51.580
So looking at it, so it look in terms of managing the logic app itself and the sort of controls and properties around that you could also have event based alerting on it being deployed and changed so again that's something you can pick up across.
NOTE Confidence: 0.883759021759033
00:46:52.370 --> 00:47:12.380
Of anything that happens, you can track out of who did Warren Wayne. So yes, you could still pick that up and have something specifically for that and tracking what happens with the logic app, so faithfully it doesn't have to be targeted specifically at the logic app. You could have across anything that happens in your entire subscription or dinner.
NOTE Confidence: 0.855761766433716
00:47:13.170 --> 00:47:29.200
Resource group for example, and filter it of all those events and be cause. They they're always created. You can't really buy passes so as long as you've got something to extract those out, then you'll be able to track that information.
NOTE Confidence: 0.882211327552795
00:47:33.020 --> 00:47:36.820
We're going to see if I can trigger something like here? Yeah.
NOTE Confidence: 0.883463680744171
00:47:52.470 --> 00:48:12.480
Good question so looking at things of their father interfaces into things like a ticket and system and how do you not spam it with the same thing happening over and over again if you're a layout is maintained your query going back to the metrics. But in the first but the way you write your query. There you have scope to see you know what my looking back over so.
NOTE Confidence: 0.892838299274445
00:48:13.270 --> 00:48:33.280
Careful I just threw that Anna is just the most basic one to get something triggered but you could actually say look at this over a longer period of time for example, and then see whether it. You know you want to fight it. They are, but you could also within that I have additional logic in the logic app for example.
NOTE Confidence: 0.894653379917145
00:48:34.370 --> 00:48:54.290
Has this already been raised in the last 5 minutes or so, if if so, then let me just add a note to see that is still on going to the same ticket rather than explaining right now new one so that you know, there's depends on how you want to handle it. But there's enough flexibility within the the whole structure of it to be able to work out how you want to deal with it.
NOTE Confidence: 0.908230066299438
00:48:58.340 --> 00:49:05.440
So I'm guessing that my alerts are still not really wanting to trigger Unfortunately. Let me see if.
NOTE Confidence: 0.871377468109131
00:49:14.460 --> 00:49:22.040
My Lord exists my alert doesn't want to filed by the looks of it. Let me just refresh that and see if those.
NOTE Confidence: 0.912038266658783
00:49:23.160 --> 00:49:24.880
And it's in your coming through.
NOTE Confidence: 0.855104982852936
00:49:28.740 --> 00:49:37.040
No get in 19 minutes, so something is not quite kicking through and not Unfortunately, the The Demo Gremlins are or get me on that one.
NOTE Confidence: 0.676866710186005
00:49:40.300 --> 00:49:40.670
Sorry.
NOTE Confidence: 0.864531338214874
00:49:42.670 --> 00:49:58.430
Uh I still triggered it down fairly low, but yeah, that might that may actually be relevant. So yeah, that could be on there. But we're not quite in any time left to to play with that, Unfortunately so.
NOTE Confidence: 0.885043501853943
00:50:09.030 --> 00:50:11.620
So that's me in terms of that just.