0
1
00:00:00,450 --> 00:00:04,109
Please note that this content is
targeted for SysOps
1

2
00:00:04,109 --> 00:00:09,300
Administrators if you're a Solutions
Architect or a developer you may want to
2

3
00:00:09,300 --> 00:00:15,179
skip over this one. Welcome back to
BackSpace Academy. In this hands-on
3

4
00:00:15,179 --> 00:00:19,500
lecture on monitoring RDS we're just
going to run through some of the tools
4

5
00:00:19,500 --> 00:00:25,830
that are available for monitoring our
RDS instances okay so our instance is
5

6
00:00:25,830 --> 00:00:30,330
now available and what we can do now is
start to have a look at some of the
6

7
00:00:30,330 --> 00:00:34,829
metrics that are being produced from it
so we click on show monitoring and then
7

8
00:00:34,829 --> 00:00:39,409
we can see our standard cloud watch
metrics so we've got CPU utilization
8

9
00:00:39,409 --> 00:00:46,319
free storage space and this is coming
from the hypervisor information so what
9

10
00:00:46,319 --> 00:00:50,159
we can also look at is our enhanced
monitoring and that is coming from an
10

11
00:00:50,159 --> 00:00:55,709
agent that is running on that actual ec2
instance in a similar way that you would
11

12
00:00:55,709 --> 00:01:00,809
have a monitoring script on an ec2
instance for example so we can actually
12

13
00:01:00,809 --> 00:01:06,659
go into here and look at enhanced
monitoring and we can see there there's
13

14
00:01:06,659 --> 00:01:12,899
a lot more lower level operating system
level information available for surround
14

15
00:01:12,899 --> 00:01:17,399
memory and file system information and
load on the system which is very
15

16
00:01:17,399 --> 00:01:22,950
important as well so this is quite a
good one to monitor number of tasks that
16

17
00:01:22,950 --> 00:01:28,740
are running and the average load as well
so what we can do is we can actually
17

18
00:01:28,740 --> 00:01:33,590
create CloudWatch alarms around this as
well
18

19
00:01:40,409 --> 00:01:46,380
so if I just go back to instances now
and we can also see in here
19

20
00:01:46,380 --> 00:01:55,860
under the information we can go to logs
and there we can see that the logs for
20

21
00:01:55,860 --> 00:02:02,310
our era running log are being recorded
and our my cycle upgrade log as well so
21

22
00:02:02,310 --> 00:02:07,920
we can download and and view those as
well we've also got RDS events so
22

23
00:02:07,920 --> 00:02:12,810
just on the left hand side here we've
got events and there are a number of
23

24
00:02:12,810 --> 00:02:18,930
things that we can look at subscribing
to so we've got some events here that
24

25
00:02:18,930 --> 00:02:23,640
I've could so the DB instance was
restarted it was created it was backed
25

26
00:02:23,640 --> 00:02:28,920
up and that has finished backing up that
instance and so we can actually go into
26

27
00:02:28,920 --> 00:02:33,510
here into event subscriptions and we can
create an event subscription just give
27

28
00:02:33,510 --> 00:02:42,959
it a name and we'll create a topic there
a new topic and we just call that test
28

29
00:02:42,959 --> 00:02:55,769
again. Just copy this user@domain
that will do and we'll select source
29

30
00:02:55,769 --> 00:02:59,639
type of instances and so we just select
say whenever an instance files over or
30

31
00:02:59,639 --> 00:03:05,040
or we have a failure of an instance we
can subscribe to that and we just create
31

32
00:03:05,040 --> 00:03:17,069
that. Okay so the final thing I'd like to
show is a new feature to RDS at the time
32

33
00:03:17,069 --> 00:03:23,280
of this video it is only in preview so
if you're looking at your RDS console
33

34
00:03:23,280 --> 00:03:28,319
and you don't see this tab on the this
menu option on the left-hand side here
34

35
00:03:28,319 --> 00:03:33,030
called performance insights don't be too
concerned about it as it will be coming
35

36
00:03:33,030 --> 00:03:39,900
to you eventually and also we've got
here an option to launch an Aurora PostGre SQL
36

37
00:03:39,900 --> 00:03:47,489
preview. So Aurora has always
been a mySQL database engine
37

38
00:03:47,489 --> 00:03:53,460
database but it's now also going to be a
PostGre SQL
38

39
00:03:53,460 --> 00:04:00,960
as well. So what we'll do is
we'll launch a PostGre SQL Aurora
39

40
00:04:00,960 --> 00:04:05,580
instance because that is what we can use
now with performance insights so I just
40

41
00:04:05,580 --> 00:04:13,800
click on that so I'll just use the
smallest class that it's available just
41

42
00:04:13,800 --> 00:04:22,860
give it a simple name now we can't use
admin for a PostGre database we use
42

43
00:04:22,860 --> 00:04:25,280
something else
43

44
00:04:39,280 --> 00:04:45,730
just give the cluster a simple name as
well and the database a simple name now
44

45
00:04:45,730 --> 00:04:53,830
I'm just going to enable enhanced
monitoring as well and I'll give the
45

46
00:04:53,830 --> 00:05:01,380
granularity of 15 seconds and we can see
here we've got an option for enabling
46

47
00:05:01,380 --> 00:05:06,670
performance inside so that's a new
feature that is currently at the time of
47

48
00:05:06,670 --> 00:05:12,640
writing or at the time of this video
being created is only available for
48

49
00:05:12,640 --> 00:05:22,980
Aurora PostGre SQL instances so
just go and launch that DB instance now
49

50
00:05:28,080 --> 00:05:33,820
and after certain amount of time that
will be up and running. Okay so our
50

51
00:05:33,820 --> 00:05:40,090
Aurora PostGre SQL database is up
and running so what I'm going to do now
51

52
00:05:40,090 --> 00:05:45,340
is just connect in to it so I'll just
grab that endpoint and jump into PG
52

53
00:05:45,340 --> 00:05:52,960
admin create a new server put the
connection in there take the
53

54
00:05:52,960 --> 00:05:57,100
5432 off the end of it and if you
don't remember how to do this just go
54

55
00:05:57,100 --> 00:06:04,930
back to the RDS section and do the labor
on post crazy sequel databases and I'll
55

56
00:06:04,930 --> 00:06:16,540
put my username and password save the
password just give it a name test two
56

57
00:06:16,540 --> 00:06:28,450
that will be fine and save okay so now
I've connected in there if I have a look
57

58
00:06:28,450 --> 00:06:33,180
at my database I should see my test two
database we'll just connect into that
58

59
00:06:33,180 --> 00:06:43,240
and that is a good go to the dashboard,
okay so I'm connected in as a user there
59

60
00:06:43,240 --> 00:06:48,850
so I should be able to now go back into
the RDS console and now if I click
60

61
00:06:48,850 --> 00:06:53,280
on performance insights which is that
new feature
61

62
00:06:55,059 --> 00:07:00,259
and now if I select I can see here I've
got my master database and my replica
62

63
00:07:00,259 --> 00:07:05,899
here, if I select that master
database I can see that there's
63

64
00:07:05,899 --> 00:07:10,519
information there of my activity of
connecting into that instance so we can
64

65
00:07:10,519 --> 00:07:17,899
see we've got a little bit more
information here from from the
65

66
00:07:17,899 --> 00:07:22,669
performance insights in particular
around load on the data based so what
66

67
00:07:22,669 --> 00:07:26,959
we've got here is is that we can we can
have a look at users as well so load by
67

68
00:07:26,959 --> 00:07:31,459
user and it gives us a lot more
granularity around what it's actually
68

69
00:07:31,459 --> 00:07:38,629
happening with our RDS Aurora instance
so that's about all I need to show you
69

70
00:07:38,629 --> 00:07:44,059
about monitoring of RDS and I'll look
forward to seeing you in the next
70

71
00:07:44,059 --> 00:07:46,209
lecture