0
1
00:00:00,330 --> 00:00:05,229
Please note that this content is
targeted for SysOps administrators. If
1

2
00:00:05,229 --> 00:00:09,820
you're a Solutions Architect or a
developer you may want to skip over this
2

3
00:00:09,820 --> 00:00:12,060
one
3

4
00:00:13,510 --> 00:00:20,660
Welcome back to BackSpace Academy. In
this lecture on monitoring RDS we'll go
4

5
00:00:20,660 --> 00:00:25,160
through the monitoring options that are
available for the RDS service we'll also
5

6
00:00:25,160 --> 00:00:29,079
look at the enhance monitoring that is
available that provides real-time
6

7
00:00:29,079 --> 00:00:34,550
monitoring of our instances we'll look
at RDS events that provide us with a
7

8
00:00:34,550 --> 00:00:39,370
unique service for RDS to alert us to
issues and we'll also look at the
8

9
00:00:39,370 --> 00:00:44,270
downloading of database log files that
are produced from the actual database
9

10
00:00:44,270 --> 00:00:51,890
engine the monitoring options that are
available for us with RDS. As with most
10

11
00:00:51,890 --> 00:00:57,260
services we have CloudWatch alarms that
can alert us to an issue we have 
11

12
00:00:57,260 --> 00:01:02,540
CloudWatch logs that we can use for archiving
of this information from CloudWatch and
12

13
00:01:02,540 --> 00:01:07,220
we can also have CloudWatch events that
become that we can use to invoke other
13

14
00:01:07,220 --> 00:01:12,110
services that we can subscribe to and
get messages from, we also have the
14

15
00:01:12,110 --> 00:01:17,590
enhanced monitoring now that is specific
to RDS and it provides real-time
15

16
00:01:17,590 --> 00:01:23,720
operating system metrics for RDS and
against specific to RDS we have the RDS
16

17
00:01:23,720 --> 00:01:28,130
events that we can subscribe to these
RDS events and we can have an SNS
17

18
00:01:28,130 --> 00:01:34,460
message sent out to us if something
occurs that is unusual we also have
18

19
00:01:34,460 --> 00:01:40,340
database log files and they are produced
by the specific database engine so you
19

20
00:01:40,340 --> 00:01:44,600
you've got mySQL that it will
produce a certain set of log files if
20

21
00:01:44,600 --> 00:01:48,710
you have SQL Server it produces it so
instead of log files as well so we're
21

22
00:01:48,710 --> 00:01:54,140
looking to how we can actually access
those and and view those another new
22

23
00:01:54,140 --> 00:01:58,520
service that we've got there is the
Amazon performance insights and that
23

24
00:01:58,520 --> 00:02:03,860
provides a lot more visualization and
some further metrics that we can use for
24

25
00:02:03,860 --> 00:02:09,429
monitoring our instances and finally we
can look at implementing cloud trail on
25

26
00:02:09,429 --> 00:02:16,459
our RDS instances and that will enable
us to record API action to our audience
26

27
00:02:16,459 --> 00:02:23,420
instances and to store that with Amazon
CloudWatch logs
27

28
00:02:23,420 --> 00:02:28,650
so RDS enhance monitoring, when it
is enabled on an instance, it will
28

29
00:02:28,650 --> 00:02:33,510
provide real-time operating system
metrics for that instance they can be
29

30
00:02:33,510 --> 00:02:37,890
viewed in the console or you can
actually view and download your cloud
30

31
00:02:37,890 --> 00:02:43,350
watch logs for those metrics it's not
available for t1 micro and m1 small
31

32
00:02:43,350 --> 00:02:49,800
instances and the cost will vary there
is a free tier usage level but if you
32

33
00:02:49,800 --> 00:02:54,720
exceed that then you are going to be
charged and so that depends on what
33

34
00:02:54,720 --> 00:02:59,160
you're monitoring interval is so how
frequently you are actually getting this
34

35
00:02:59,160 --> 00:03:02,970
information and logging that information
the number of instances that you'll be
35

36
00:03:02,970 --> 00:03:07,860
monitoring and the amount of activity
that needs to be reported so for example
36

37
00:03:07,860 --> 00:03:12,840
if you're doing compute metrics and
you've got a compute intensive instance
37

38
00:03:12,840 --> 00:03:17,040
or large instance that's doing a lot of
compute operations then there may be
38

39
00:03:17,040 --> 00:03:21,270
more activity to report so you need to
take that into consideration if you're
39

40
00:03:21,270 --> 00:03:30,330
looking to stay under the free tier RDS
events we can subscribe to those and
40

41
00:03:30,330 --> 00:03:36,420
they will trigger an SNS notification
for us there are multiple event types
41

42
00:03:36,420 --> 00:03:42,420
and within the event types there are
multiple types as well within that so
42

43
00:03:42,420 --> 00:03:46,890
there was a very broad range of events
that we can subscribe to and it provides
43

44
00:03:46,890 --> 00:03:52,020
a very good granularity if we're looking
for certain out of the ordinary events
44

45
00:03:52,020 --> 00:03:57,630
that we want to be alerted to so we can
view those events again not only via the
45

46
00:03:57,630 --> 00:04:03,000
SNS notification service but we also can
view them with the RDS console and the
46

47
00:04:03,000 --> 00:04:11,760
command-line interface or the API or SDK
so database log files they are produced
47

48
00:04:11,760 --> 00:04:17,970
by the specific database engine that we
are using and that that varies depending
48

49
00:04:17,970 --> 00:04:22,260
on what engine we are using for example
mySQL you can see there we've got
49

50
00:04:22,260 --> 00:04:26,910
error slow query and general logs
whereas Oracle it doesn't have error
50

51
00:04:26,910 --> 00:04:31,500
logs available so the logs that are
available or the log files that are
51

52
00:04:31,500 --> 00:04:36,750
available to us depends on what database
engine we're using so those log files
52

53
00:04:36,750 --> 00:04:39,450
like
be downloaded and viewed using the RDS
53

54
00:04:39,450 --> 00:04:46,260
console the command-line interface or
the API tools and transaction logs are
54

55
00:04:46,260 --> 00:04:51,060
not supported so we're looking about
error logs and general logs but we're
55

56
00:04:51,060 --> 00:04:55,530
not looking at actual transaction logs
they're not supported so that brings us
56

57
00:04:55,530 --> 00:05:00,570
to the end of this lecture and the best
way to really understand this is to
57

58
00:05:00,570 --> 00:05:05,250
start to use it so we'll have a hands-on
les lesson coming up next and I'll see
58

59
00:05:05,250 --> 00:05:07,790
you in that one