1
00:00:00,330 --> 00:00:06,090
So let's look at the Gryphon, a Matrix Prometheus dashboard now to back into Agraféna configuration

2
00:00:06,090 --> 00:00:11,640
data sources, Prometheus dashboards, cofounder metrics, they import that.

3
00:00:11,790 --> 00:00:13,890
OK, so this is not going to work straight away.

4
00:00:13,920 --> 00:00:14,440
Let's look at it.

5
00:00:14,570 --> 00:00:16,379
OK, lots of things missing.

6
00:00:16,770 --> 00:00:24,660
If we look at one of the visualizations he is looking for, job equals Carafano just for the one.

7
00:00:25,110 --> 00:00:27,740
A job equals profile.

8
00:00:28,140 --> 00:00:30,000
OK, so we go to the Explore tab.

9
00:00:30,720 --> 00:00:33,780
Discard Prometheus Matrix browser.

10
00:00:33,810 --> 00:00:34,660
Look good job.

11
00:00:34,680 --> 00:00:39,480
We only have jobs for Node and Prometheus, so that dashboard needs a job.

12
00:00:39,480 --> 00:00:45,870
Mega-fauna now the Prometheus service and the node exporter both provide these endpoints that expose

13
00:00:45,870 --> 00:00:52,140
the metrics that these services are meant to expose or to show those so on your Bafana's server, you

14
00:00:52,140 --> 00:01:03,400
can view those so curl HTP Colon Slash Slash one two seven zero zero one colon 1990 slash metrics enter.

15
00:01:03,420 --> 00:01:08,940
That is a lot of information in that response, but that is the information that you will find when

16
00:01:08,940 --> 00:01:11,130
you query the Prometheus job.

17
00:01:11,280 --> 00:01:16,950
For example, if I scroll up, here's something Prometheus, TSB storage, block sports, I'll just

18
00:01:16,950 --> 00:01:18,910
highlight that so it copies it to the clipboard.

19
00:01:18,930 --> 00:01:24,660
Now, if I thought that into there, we could say that it is one of the things that we can see in Prometheus,

20
00:01:24,840 --> 00:01:25,890
and that's the value.

21
00:01:25,920 --> 00:01:28,850
So it's a key space value kind of set up.

22
00:01:28,880 --> 00:01:30,790
OK, so there's one for everything now.

23
00:01:30,790 --> 00:01:32,400
It's the same thing for Node.

24
00:01:32,460 --> 00:01:39,570
If I do a query on Port nine 100GB metrics, we're getting all the keys and the values for the node

25
00:01:39,570 --> 00:01:40,160
exporter.

26
00:01:40,180 --> 00:01:41,240
I just scroll up.

27
00:01:41,250 --> 00:01:45,480
There's some poor node node system, do you state or do a search for that?

28
00:01:45,510 --> 00:01:48,540
And we go in node system D unit state job node.

29
00:01:48,690 --> 00:01:54,750
So it just so happens that the Gryphon US server, when it's running, also exposes its own metrics

30
00:01:54,750 --> 00:01:59,940
endpoint and that is at Port 3000 slash metrics.

31
00:01:59,940 --> 00:02:00,450
And we go.

32
00:02:00,480 --> 00:02:05,670
So this is a whole lot of Gravano metric information that we can show in Prometheus.

33
00:02:05,670 --> 00:02:08,039
We'll create a new script target in Prometheus.

34
00:02:08,039 --> 00:02:10,889
It will also query this Carvana metrics endpoint.

35
00:02:11,039 --> 00:02:15,960
So we need to open up the Prometheus configuration file that is in the folder side.

36
00:02:16,230 --> 00:02:20,500
ATC Prometheus Ellis LRH.

37
00:02:20,530 --> 00:02:23,400
This is where Prometheus was installed at Prometheus.

38
00:02:23,430 --> 00:02:26,940
That Prometheus why IMO is the configuration space suit?

39
00:02:27,000 --> 00:02:28,710
I know Prometheus.

40
00:02:28,710 --> 00:02:30,870
Why HTML if we scroll down?

41
00:02:32,050 --> 00:02:39,070
Into this scrape configs section here, I'll just scroll further there to scrape configs with a job

42
00:02:39,070 --> 00:02:41,970
name Prometheus and another one job name.

43
00:02:42,020 --> 00:02:48,510
Note this is what we're saying to the Prometheus job is getting its information from local hosts 1990,

44
00:02:48,520 --> 00:02:51,440
and it's just doing a search for slash metrics.

45
00:02:51,460 --> 00:02:56,240
The node is getting its information from local 9100 slash metrics.

46
00:02:56,260 --> 00:03:01,510
So what you're going to do is create another job name for Gravano called Bafana that will take its information

47
00:03:01,510 --> 00:03:03,000
from local hosts 3000.

48
00:03:03,010 --> 00:03:07,180
So put your cursor at the bottom of that highlight just that job name there.

49
00:03:07,210 --> 00:03:11,200
Make sure all the white space is selected and we can put the cursor up.

50
00:03:11,290 --> 00:03:14,620
I can just add an extra space in their job name Bafana.

51
00:03:14,650 --> 00:03:18,340
Throw down static configs at thousand.

52
00:03:18,460 --> 00:03:18,940
Very good.

53
00:03:19,000 --> 00:03:22,600
Now you can delete those to comment lines if you want in nano.

54
00:03:22,660 --> 00:03:27,440
It is control, OK, and then control kigen that deletes lines, but that's optional.

55
00:03:27,460 --> 00:03:32,360
Anyway, it's not the job name Gravano, and the static config is local host 3000.

56
00:03:32,380 --> 00:03:39,610
That is the default port of Kafala when you first install it and is in the scrape config section in

57
00:03:39,610 --> 00:03:43,600
Prometheus Y.M.C.A. Control X to save gas to save the buffer.

58
00:03:43,690 --> 00:03:46,030
Press enter its restart Prometheus.

59
00:03:47,970 --> 00:03:49,440
Double check its status.

60
00:03:50,530 --> 00:03:53,360
I go that's running control C to get out of that.

61
00:03:53,380 --> 00:03:59,130
Now if I just refreshed this whole screen to rug click and press refresh and then I press metrics browser

62
00:03:59,170 --> 00:04:02,240
have jobs selected, we could see this new job for Bafana.

63
00:04:02,310 --> 00:04:09,190
OK, so if I go back into the dashboards now, dashboards manage grandfather metrics there.

64
00:04:10,100 --> 00:04:13,510
We're now starting to get data, so those queries are actually starting to work.

65
00:04:13,600 --> 00:04:16,320
I do a search for the last five minutes.

66
00:04:16,360 --> 00:04:17,740
We're getting most information.

67
00:04:18,029 --> 00:04:18,279
Have a look.

68
00:04:18,279 --> 00:04:20,230
What's wrong with hasty status codes?

69
00:04:20,730 --> 00:04:28,920
They so first thing hasty http request total and is replaced that with this text will be on my documentation.

70
00:04:28,930 --> 00:04:30,070
We now get a graph.

71
00:04:30,100 --> 00:04:35,440
So two things have changed in the later version that status code now has done to school between the

72
00:04:35,440 --> 00:04:42,490
two words and also that value is often a heist http request duration seconds second, some so we can

73
00:04:42,610 --> 00:04:43,960
apply that never go.

74
00:04:45,030 --> 00:04:51,210
We have a new graph which is showing the requests per second and the different status codes.

75
00:04:51,270 --> 00:04:53,130
Now we look at this one here.

76
00:04:53,140 --> 00:04:59,610
Prometheus Alerts Press eight added that it's no longer alerts, so delete that and let's just put a

77
00:04:59,610 --> 00:05:06,180
bracket open up and start typing alert and you'll get some things that it could be.

78
00:05:06,210 --> 00:05:09,300
Now I'm guessing that it's Gryffindor alerting active.

79
00:05:09,360 --> 00:05:11,880
Let's take a look out of that, and that looks right.

80
00:05:11,930 --> 00:05:14,100
There are zero alerts firing right now.

81
00:05:14,130 --> 00:05:15,420
OK, so apply that.

82
00:05:15,540 --> 00:05:16,560
Okay, so that works.

83
00:05:16,710 --> 00:05:23,450
Now the last one, most use handlers edit sort top K Handler page to request total.

84
00:05:23,460 --> 00:05:29,520
So once again change that HTP request total to Safana to be to the second.

85
00:05:30,090 --> 00:05:30,510
There we go.

86
00:05:30,510 --> 00:05:36,300
We start to see a table there now so we can also apply that never go because some information coming

87
00:05:36,300 --> 00:05:36,600
through.

88
00:05:36,690 --> 00:05:39,510
Now this is a very basic Griffon Up Metrics dashboard.

89
00:05:39,720 --> 00:05:43,970
If you search on official Gryffindor dashboard website, there might be other options to choose from.

90
00:05:43,980 --> 00:05:49,370
But anyway, let's just quickly what happens when you try to install a dashboard in Gravano Things?

91
00:05:49,380 --> 00:05:53,760
I look at work because of the later versions, so you have to apply a bit of guesswork and you just

92
00:05:53,760 --> 00:05:55,140
get better at that with experience.

93
00:05:55,140 --> 00:05:58,110
Anyway, save that overwrite anyway.

94
00:05:58,110 --> 00:06:01,980
The next video will install the Prometheus Not Explorer on our basketball server.

95
00:06:02,040 --> 00:06:02,490
Excellent.

