1
00:00:00,510 --> 00:00:00,960
Excellent.

2
00:00:01,050 --> 00:00:06,840
So far, we have in flux DBI version to install, we have a telegraph collector collecting stats and

3
00:00:06,840 --> 00:00:12,060
sending it to influx Digby, and we can visualize that through the complexity without a source in Gravano.

4
00:00:12,120 --> 00:00:18,570
Now, like how we've set up other data sources in the past, you can have one main server such as Prometheus

5
00:00:18,570 --> 00:00:23,070
or Loki, and have many collectors or from Taylor, for example.

6
00:00:23,070 --> 00:00:27,600
For Prometheus, it's not exporters, and there are many other kinds of exporter's for Prometheus,

7
00:00:27,600 --> 00:00:33,390
not just not exporters or the Gryphon metrics, end point or any other endpoints that Prometheus can

8
00:00:33,390 --> 00:00:33,720
read.

9
00:00:33,720 --> 00:00:39,480
For Influx DB, we can have multiple telegraphs, so I can set up telegraph on my moskvy or server and

10
00:00:39,480 --> 00:00:46,830
pointed to either the VPC IP address of the influx DB or the external address, or I can have telegraphs

11
00:00:46,830 --> 00:00:50,280
on all the servers that I got access to or sending to Fox DB.

12
00:00:50,310 --> 00:00:54,010
Now I'm not going to show you how to do that in this video if you do want to ever do that.

13
00:00:54,030 --> 00:00:54,840
It's not that hard.

14
00:00:54,840 --> 00:00:59,940
You just copy the instructions that we use for the first telegraph that we installed, and you would

15
00:00:59,940 --> 00:01:06,450
configure the URL that you're sending the data to in your telegraph configuration there and whichever

16
00:01:06,450 --> 00:01:08,070
inputs you want to collect.

17
00:01:08,100 --> 00:01:11,250
So in this video, I'll be introducing you to S and MPD.

18
00:01:11,280 --> 00:01:13,250
OK, so there's no need for that.

19
00:01:13,260 --> 00:01:15,800
You can do that if you want to in your own time.

20
00:01:15,810 --> 00:01:18,270
But in this video, I'll introduce you to S&P now.

21
00:01:18,270 --> 00:01:24,600
SMP Simple Network Management Protocol is a protocol that's been around since before the internet went

22
00:01:24,600 --> 00:01:25,080
public.

23
00:01:25,140 --> 00:01:28,860
So it's very old and there's a lot of devices that still support it.

24
00:01:28,890 --> 00:01:36,180
Now it's useful in those cases where you can't install a service such as routers or switches or printers,

25
00:01:36,180 --> 00:01:39,210
or even servers and workstations can support SMP.

26
00:01:39,240 --> 00:01:44,580
You'll find a lot of hardware in corporate environments where you can't actually install Telegraph Electron

27
00:01:44,580 --> 00:01:46,970
to or we can't install prompter onto.

28
00:01:46,980 --> 00:01:48,390
It is not an operating system.

29
00:01:48,390 --> 00:01:52,260
We can do that, so those devices may provide data through an internet interface.

30
00:01:52,320 --> 00:01:57,120
Now also, since you properly don't have A. an MP device on your own network that you can use, I'll

31
00:01:57,120 --> 00:02:02,850
show you how to install an SMP daemon on Ubuntu twenty point zero four so that we can at least have

32
00:02:02,850 --> 00:02:03,810
some experience with it.

33
00:02:04,020 --> 00:02:10,199
OK, so I'm going to install the SNP daemon on the same server as my influx DB server.

34
00:02:10,259 --> 00:02:14,570
OK, so log on to your influx DB server and we'll install the SMP demon on it.

35
00:02:14,640 --> 00:02:14,950
OK.

36
00:02:14,970 --> 00:02:22,710
Some of my influx DB server, so install SMP, S&P Dow and S&P MIPS Down Downloader because we use all

37
00:02:22,710 --> 00:02:31,830
those right click to place and enter then yes, now I'm doing this just so that we can show S&P because

38
00:02:31,830 --> 00:02:35,430
you're very unlikely to have an actual S&P device on your network.

39
00:02:36,330 --> 00:02:40,560
So this way of doing it is more reproducible while you're learning, OK, so it's normally started when

40
00:02:40,560 --> 00:02:44,070
we've installed it so we can check it status active running.

41
00:02:44,100 --> 00:02:44,430
Excellent.

42
00:02:44,430 --> 00:02:52,200
OK, now we can do a simple test query, so copy that S&P Walke version to see the community is public.

43
00:02:52,200 --> 00:02:58,380
One two seven zero zero one So that's this computer dot means give me everything, and we got a lot

44
00:02:58,380 --> 00:02:59,880
of data being returned.

45
00:03:00,030 --> 00:03:04,460
Now, it's important to note that the data returned is showing our ID numbers.

46
00:03:04,470 --> 00:03:06,060
So this is one way it's shown.

47
00:03:06,060 --> 00:03:09,090
Also, those numbers equals a value.

48
00:03:09,150 --> 00:03:13,170
So as we say here, ISO equals data type in a value sometimes set.

49
00:03:13,170 --> 00:03:15,880
Why not say, Oh, sorry, that might say no one doesn't really matter.

50
00:03:15,900 --> 00:03:21,150
What's important is that when we continue to set up the Telegraph collector for S&P, it's going to

51
00:03:21,150 --> 00:03:27,000
be doing search on what's called MIPS and maybe stands for management information base, but maybe some

52
00:03:27,030 --> 00:03:29,520
other form of a string like that.

53
00:03:29,520 --> 00:03:34,500
And when we do the telegraph configuration, it will be looking up the string version.

54
00:03:34,950 --> 00:03:37,780
So same with this one and if table as well.

55
00:03:37,800 --> 00:03:42,330
So it's important to make sure MIPS work on your SMP daemon.

56
00:03:42,340 --> 00:03:49,260
So one way we can do that is to go into a file called SMP dot com, not as S&P dot com.

57
00:03:49,260 --> 00:03:54,390
So copy that ciudadano ADC, SMP, SMP, dconf into.

58
00:03:54,420 --> 00:03:57,510
Now scroll down and will comment at that line.

59
00:03:57,540 --> 00:03:58,620
So it's now hash.

60
00:03:58,740 --> 00:04:01,120
Maybe just comment to the tropics to save?

61
00:04:01,140 --> 00:04:01,680
Yes.

62
00:04:02,070 --> 00:04:04,350
Now if we do that same query again.

63
00:04:04,950 --> 00:04:09,270
Version two C. S. Public 127 zero zero one dot, which means everything.

64
00:04:09,360 --> 00:04:12,950
Each line showing the MAIB description no longer the numbers.

65
00:04:12,960 --> 00:04:18,019
So when we set up Telegraph, our configuration will be searching for map descriptions, for example.

66
00:04:18,029 --> 00:04:19,680
So and you can see that down here.

67
00:04:19,680 --> 00:04:24,720
So we're looking for information, maybe if description, so we can actually search one of those directly.

68
00:04:24,730 --> 00:04:26,050
So why just copy that?

69
00:04:26,070 --> 00:04:27,190
We'll see if that works.

70
00:04:27,220 --> 00:04:30,540
OK, so doing that query again, we'll get rid of that dot at the end.

71
00:04:30,720 --> 00:04:35,280
And if I just put in that whole query, press enter and returns what I'm looking for now.

72
00:04:35,310 --> 00:04:40,760
You can also just get rid of the RF C one two three bit there at the beginning to even do that.

73
00:04:40,770 --> 00:04:41,470
And it's the same.

74
00:04:41,490 --> 00:04:41,850
OK.

75
00:04:41,880 --> 00:04:44,760
That's just a little bit of information about SMP for you there.

76
00:04:44,760 --> 00:04:48,780
S&P's a very large subject, but I'm just showing you the beginnings to help me get started.

77
00:04:48,840 --> 00:04:52,890
OK, now let's open up our telegraph configuration like that.

78
00:04:52,890 --> 00:04:55,770
And if we just scroll down, look at the input section.

79
00:04:55,770 --> 00:04:59,220
So we have quite a few inputs already from the last videos.

80
00:04:59,640 --> 00:05:01,080
Another one for S&P.

81
00:05:01,230 --> 00:05:09,600
So copy, I've got there, so I want to copy that whole lot right click and it's just a minimal S&P

82
00:05:09,600 --> 00:05:11,340
input configuration there.

83
00:05:11,730 --> 00:05:17,970
That's the address that we checking one 27 zero zero one call one six one and it uses the UDP protocol.

84
00:05:18,000 --> 00:05:18,810
OK, so that's good.

85
00:05:18,810 --> 00:05:23,490
That's going to do some simple queries of the S&P Daymond that we just installed on our local server

86
00:05:23,490 --> 00:05:29,280
here, the Clucks DB server, and we'll be able to see that information first influx DB and then in

87
00:05:29,460 --> 00:05:30,060
Safana.

88
00:05:30,060 --> 00:05:31,900
So control X to save that.

89
00:05:31,930 --> 00:05:35,460
Yes, OK, so now to restart the telegraph service.

90
00:05:35,580 --> 00:05:45,360
So sudo service telegraph restart a status, then it looks pretty good so far.

91
00:05:45,540 --> 00:05:47,490
So any errors, I'll see.

92
00:05:47,540 --> 00:05:50,630
Now let's go into influx and see what we've got.

93
00:05:50,640 --> 00:05:53,210
So in your influx DB, go to explore.

94
00:05:53,220 --> 00:05:58,730
And if we look at this measurements section, we should start to see some S&P.

95
00:05:58,740 --> 00:06:02,670
There isn't much there at the moment, showing up as just the uptime, maybe.

96
00:06:02,790 --> 00:06:05,580
So I submit that it's showing uptime here.

97
00:06:05,640 --> 00:06:09,390
I look at the query there that's see sometimes coming from this name.

98
00:06:09,390 --> 00:06:11,210
Does uptime also in there?

99
00:06:11,220 --> 00:06:17,100
We have agent host, host and source source here has come up.

100
00:06:17,100 --> 00:06:19,290
It's a tag is tag equals true.

101
00:06:19,320 --> 00:06:22,490
So we can also use that the same as the host, really.

102
00:06:23,430 --> 00:06:25,040
But that is a table if you like.

103
00:06:25,050 --> 00:06:30,120
But anyway, we're not seeing any information yet for if table or if description.

104
00:06:30,120 --> 00:06:36,090
And the reason for that is because by default, when we install the S&P D on a but to the information

105
00:06:36,090 --> 00:06:38,670
S&P D will return is quite restricted.

106
00:06:38,670 --> 00:06:42,990
It's restricted to decides with that prefix or that prefix.

107
00:06:42,990 --> 00:06:48,360
What we'll need to do is change it so that it returns a larger range of our IDs.

108
00:06:48,360 --> 00:06:52,920
So very quickly, let's just try and search for maybe if table.

109
00:06:52,930 --> 00:06:58,950
So we could verify that it's not returning anything by typing that it's an empty table command version

110
00:06:58,950 --> 00:07:00,570
to see public local IP.

111
00:07:00,570 --> 00:07:07,170
If Table says no entries, so let's change the allowable ID prefix in the S&P Daymond configuration.

112
00:07:07,180 --> 00:07:12,420
So this time it's S&P D dot com until and if we scroll down.

113
00:07:14,500 --> 00:07:20,140
And we can see down here where it describes the view, we can comment at that line because it's not

114
00:07:20,140 --> 00:07:23,460
going to be necessary and just remove this last one.

115
00:07:23,470 --> 00:07:25,830
So control x, yes.

116
00:07:25,840 --> 00:07:33,160
And now to restart the S&P Demon Sudo service, it's an the restart.

117
00:07:33,160 --> 00:07:37,450
And now we'll for that query again if table and we get some data.

118
00:07:37,480 --> 00:07:43,600
Okay, so that means after the moment to the graph should have caught up and we'll start to see some

119
00:07:43,600 --> 00:07:51,970
more information on the interface in flux DB and we start to see all of those values being returned

120
00:07:51,970 --> 00:07:53,440
through if table there.

121
00:07:53,950 --> 00:08:00,580
So for just get rid of that good if description and if index we look at if description, we can look

122
00:08:00,580 --> 00:08:04,020
at each Ethernet device that our server has bound.

123
00:08:04,030 --> 00:08:05,950
So I'll just get rid of that submit.

124
00:08:06,020 --> 00:08:11,480
OK, so we can see that that if table query is now working inside the Telegraph, collect any information

125
00:08:11,480 --> 00:08:13,030
that's going to in flux DB.

126
00:08:13,060 --> 00:08:15,070
So if we just copy that script.

127
00:08:16,160 --> 00:08:21,470
They can put that into Carafano, so explore influx TB paste.

128
00:08:21,620 --> 00:08:24,410
Click out of that unsupported import type main.

129
00:08:24,440 --> 00:08:25,100
Doesn't matter.

130
00:08:25,110 --> 00:08:28,790
Let's just get rid of that one for now on query.

131
00:08:28,790 --> 00:08:29,590
And there we go.

132
00:08:29,600 --> 00:08:32,150
We start to see all the information coming through.

133
00:08:32,179 --> 00:08:38,929
We'll use this information in the next few videos to create a dashboard for S&P inside Gryphon.

134
00:08:39,110 --> 00:08:44,800
OK, so you should now be saying that S&P information inside Carafano or the influx daily data source

135
00:08:44,810 --> 00:08:46,750
now note how this has been set up.

136
00:08:46,760 --> 00:08:53,810
The S&P D is serving data that has been requested from Telegraph, so the Telegraph agent is periodically

137
00:08:53,810 --> 00:08:55,270
requesting data from it.

138
00:08:55,370 --> 00:08:55,940
They pay data.

139
00:08:56,090 --> 00:09:01,530
We can set up Telegraph to query multiple S&P Demons on different servers.

140
00:09:01,550 --> 00:09:08,270
So the next video of set up another is an MPD on my Moscow Agraféna server, so that we can see S&P

141
00:09:08,300 --> 00:09:12,980
data from multiple servers through the one telegraph because they will create a simple dashboard, Agraféna,

142
00:09:12,980 --> 00:09:14,420
where we can view all three servers.

143
00:09:14,810 --> 00:09:15,260
Excellent.

