11 videos 📅 2025-01-06 09:00:00 Asia/Brunei
2:33
2025-01-06 13:08:28
3:21
2025-01-08 09:13:02
4:34
2025-01-08 09:31:44
22:26
2025-01-08 09:34:32
22:27
2025-01-08 10:16:32
24:59
2025-01-08 11:36:15
6:37
2025-01-08 14:09:18
17:55
2025-01-08 18:20:43
16:28
2025-01-08 18:20:43
34:39
2025-01-08 21:21:43
34:51
2025-01-08 21:21:44

Visit the Kafka for Administrator course recordings page

United Arab Emirates - Kafka for Administrators

                WEBVTT

00:00:01.000 --> 00:00:09.060
I just want to do one more thing you see it here the query or the metrics browser.

00:00:09.960 --> 00:00:17.400
So usually they use count they do all the stuff if you want to explore more or more

00:00:17.400 --> 00:00:22.180
matrices on how to handle it we need to learn about how we can handle a graph on a but

00:00:22.180 --> 00:00:27.680
I am using a sample example of one of the metric what is a partition count of

00:00:27.680 --> 00:00:34.920
how many partings are there on this server okay since this is saying like in this

00:00:34.920 --> 00:00:42.400
clusters I have only one broker that's where it is going one okay one server

00:00:45.160 --> 00:00:53.500
yeah if you see previously there was no request now since they were you

00:00:53.500 --> 00:01:03.580
want to see the data in your thing okay Janice is able to see it yeah

00:01:10.920 --> 00:01:22.980
once we do some action on the topics all this stuff then you can see the data coming in the

00:01:22.980 --> 00:01:33.300
click on it edit it and you will be able to try it out and let me know if we have issues

00:01:41.860 --> 00:01:50.080
everybody able to see the data coming in somebody does any operation there like kind

00:01:50.080 --> 00:01:58.920
of getting the messages in and out then the data will appear and there is a delay

00:01:58.920 --> 00:02:03.760
1 to 2 minutes but monitoring is primarily

00:02:26.080 --> 00:02:30.980
So, any questions any doubts or any issue while you are doing it?

00:03:04.280 --> 00:03:30.960
No, this is actually coming from the confluence, yeah, that's my cloud, this one here, which one, this one, this one is in your local, but data is driven from the cloud.

00:03:30.980 --> 00:03:44.020
Right. Yeah, you're sitting there, you can search a dashboard, my dashboard. Oh, if you want to access this dashboard, it should be in the cloud, because this is my local.

00:03:46.240 --> 00:03:53.920
If you want to do it kind of like somebody you want to show right or if somebody has to access, then you need to put it in your cloud.

00:03:55.400 --> 00:04:04.640
Then tie it up, then people can say from there you can, but this is my local you cannot be able to, you will not be able to access it, but.

00:04:11.400 --> 00:04:12.800
So.

00:04:15.820 --> 00:04:16.020
So.

00:04:17.160 --> 00:04:17.720
Yeah.

00:04:25.900 --> 00:04:37.060
These are open source, the only thing is you need to have the hardware, ideally a VM to run, you can run both of them on the same server.

00:04:37.060 --> 00:04:49.060
But in general practice right, they run Prometheus on one server and Grafana on another server to make sure if something goes wrong, at least you have the data on the Grafana.

00:04:50.680 --> 00:04:51.200
Yeah.

00:04:55.360 --> 00:05:06.960
This is in general like you can use, there are so many tools to visualize but Grafana is the most popular one for visualizing because it's an open source it has.

00:05:06.960 --> 00:05:20.940
You can see like people building all the dashboards we can utilize them or you can take an inspiration from them and build our own build our own dashboards for monitoring it and trying to see if something is going wrong.

00:05:22.740 --> 00:05:23.080
Yeah.

00:05:23.080 --> 00:05:30.900
So in my previous order we used to have the, how many orders are coming in, how many orders are going down.

00:05:31.860 --> 00:05:33.400
So on a high level.

00:05:34.880 --> 00:05:35.900
We used to use that.

00:05:37.320 --> 00:05:42.460
I mean there's like no direct simple way.

00:05:44.200 --> 00:05:44.620
Yes.

00:05:48.740 --> 00:05:49.700
From the.

00:05:51.860 --> 00:05:52.060
Yeah.

00:05:53.780 --> 00:06:00.040
There will be no simple thing but yeah, like, if you want to get something you have to use something like this tools.

00:06:01.340 --> 00:06:09.960
Are you utilize the conference load itself, but they will have limited number of things they will not have the more like to see this one.

00:06:10.680 --> 00:06:20.760
Here we have a limited list throughput production the major ones usually what they do, but not every matrix will be there. So it is very limited.

00:06:20.760 --> 00:06:22.040
Well,

00:06:27.160 --> 00:06:29.320
the audit loss. No,

00:06:30.740 --> 00:06:35.260
you will not be able to get audit logs from the

00:06:35.260 --> 00:06:42.420
conference because they will not allow you to get it

00:06:42.420 --> 00:06:47.920
until unless you have your own cloud. I mean, this one you installed in your.

00:06:48.920 --> 00:06:51.000
There are two ways to do it one.

00:06:51.820 --> 00:07:03.460
Get the cloud from the conflict or use the conflict cost cut to install in your own on print. If you do it on time then you'll able to do it because you are holding the loss.

00:07:06.400 --> 00:07:07.320
Yeah.

00:07:11.440 --> 00:07:12.920
If you have those logs.

00:07:23.460 --> 00:07:23.920
No.

00:07:27.960 --> 00:07:35.920
Yeah, if you are. That's what I'm saying. So yeah, that will do actually that is another session we can do it.

00:07:37.440 --> 00:07:40.800
But conflict, I'm not sure how they do it or how they pull it.

00:07:41.540 --> 00:07:48.000
But if we have our own Kafka broker in our on frame or in our cloud.

00:07:48.740 --> 00:07:53.780
By default Kafka emits some of the matrices, I will show it on the next session.

00:07:54.720 --> 00:07:59.000
So basically you can install it to see the.

00:08:00.080 --> 00:08:02.180
Have, have added for the next session.

00:08:02.640 --> 00:08:03.640
It's called

00:08:07.100 --> 00:08:12.120
JMX basically Java emits some so Kafka is built on Java.

00:08:13.220 --> 00:08:24.820
Since it is on Java, what we can do is we can use this JMX Prometheus Java agent to publish to one of the thing.

00:08:25.220 --> 00:08:33.480
And from there, we can put those details to the Prometheus, and we can manage whatever yourself right.

00:08:33.480 --> 00:08:41.800
How many people, I mean, how many topics got created, whether we have modified something, but that we need to use.

00:08:42.320 --> 00:08:44.060
You need to have to write the rules.

00:08:45.240 --> 00:08:51.940
Seeing that what metric you want to capture and from there, what you want to take it up.

00:08:52.020 --> 00:08:53.580
There is no direct way as of now.

00:08:54.080 --> 00:08:57.480
So we have to do kind of like this.

00:08:57.480 --> 00:09:02.720
Let me show you.

00:09:13.060 --> 00:09:14.400
Yeah.

00:09:16.480 --> 00:09:21.580
Yeah, Melon maker is helpful to replicate or.

00:09:22.160 --> 00:09:25.820
Let's say I have one cluster of.

00:09:26.460 --> 00:09:28.000
Servers in one location.

00:09:29.000 --> 00:09:31.860
And I want to replicate it, let's say in an on frame.

00:09:32.100 --> 00:09:33.360
I want to take it the whole.

00:09:34.040 --> 00:09:38.520
We can use a mirror maker to replicate the whole thing to the other cluster.

00:09:38.520 --> 00:09:45.360
Like the whole you can copy the whole content of the another cluster, another server or another cluster.

00:09:47.680 --> 00:09:48.420
No.

00:09:52.640 --> 00:09:56.220
So replication is done as part of in.

00:09:57.240 --> 00:09:58.640
It's right now.

00:10:03.340 --> 00:10:03.900
Okay.

00:10:09.460 --> 00:10:11.480
Even we do mirror.

00:10:12.360 --> 00:10:13.240
You do mirror.

00:10:14.040 --> 00:10:15.020
Mirror in the sense.

00:10:16.160 --> 00:10:16.740
Inside a cluster.

00:10:17.100 --> 00:10:17.900
Let's say I have five.

00:10:20.040 --> 00:10:21.780
Brokers knows how to replicate.

00:10:21.780 --> 00:10:27.340
If it is a Joe Piper, Joe Piper says if it is fast, they internally know how to replicate.

00:10:28.020 --> 00:10:31.900
But if this all to the different cluster, which is residing in.

00:10:32.740 --> 00:10:35.880
Maybe in different cloud or in different data center.

00:10:36.700 --> 00:10:38.620
Then you want to replicate from here to here.

00:10:39.120 --> 00:10:40.860
Then the bridge is the middle.

00:10:40.860 --> 00:10:41.300
So.

00:10:44.520 --> 00:10:47.560
The maker is useful to do between two places.

00:10:49.500 --> 00:10:50.680
All together in a different.

00:10:52.920 --> 00:10:54.060
I mean, somebody's.

00:10:54.100 --> 00:10:57.780
I mean, one is managing, let's say one is managing five servers.

00:10:57.940 --> 00:11:02.980
The other is managing a different region or a different data center or a different flow.

00:11:03.480 --> 00:11:07.120
But if you want to make up both of them same and use kind of.

00:11:11.220 --> 00:11:13.120
Replicator is helpful in.

00:11:15.040 --> 00:11:24.340
I mean, the replication, whatever happens in between the brokers, it is done by or usually taken care by Joe Piper or.

00:11:25.280 --> 00:11:31.440
But if you want to do it in a different location or something like that, this cannot manage.

00:11:34.460 --> 00:11:35.020
Yes.

00:11:39.540 --> 00:11:45.020
You talked about the how many people are the matrices in terms of audit loss, right?

00:11:45.480 --> 00:11:47.640
You can do that, but.

00:11:48.940 --> 00:11:50.720
You need to kind of write rules.

00:11:50.940 --> 00:11:54.340
What type of data you want to take it out.

00:11:55.300 --> 00:11:57.200
And how you want to do it.

00:11:57.320 --> 00:11:58.920
Then based on the rules.

00:11:59.680 --> 00:12:06.680
The GMX will emit those to some from with a server and from there you can put it into.

00:12:07.420 --> 00:12:10.140
So we need to kind of.

00:12:10.900 --> 00:12:12.780
Add similar to this.

00:12:13.800 --> 00:12:15.500
As of now, like.

00:12:16.080 --> 00:12:19.420
But audit logs to the Grafana, I haven't done anything.

00:12:20.920 --> 00:12:25.220
In my arms, but that we can kind of.

00:12:25.220 --> 00:12:26.040
Take it and.

00:12:26.640 --> 00:12:32.460
But in order to do that, you need to make sure that the audit logging is enabled and the audit logging is there.

00:12:32.580 --> 00:12:34.660
I'm not so confident is giving you the audit logs.

00:12:36.340 --> 00:12:37.720
But they will have their own satellite.

00:12:38.080 --> 00:12:42.900
They can actually go into the server and it is being administered by.

00:12:43.460 --> 00:12:48.620
They can like go to their own Kubernetes cluster, log into it and see what is happening.

00:12:49.160 --> 00:12:50.760
But I don't think they will give you the.

00:12:51.660 --> 00:12:55.520
I don't think we are asking for the control plane.

00:12:55.800 --> 00:13:00.760
I'm just asking for the portal activity logs.

00:13:02.200 --> 00:13:03.800
Oh, the admin activity logs.

00:13:05.280 --> 00:13:07.120
That should be.

00:13:07.420 --> 00:13:09.680
I think I only see.

00:13:12.680 --> 00:13:13.480
Yeah.

00:13:14.780 --> 00:13:16.060
Those logs I don't think.

00:13:17.460 --> 00:13:18.000
We have it.

00:13:18.000 --> 00:13:20.880
I mean, since from my side, I don't have it.

00:13:20.880 --> 00:13:27.080
But generally, if you still want to know, like, what is happening on this, that is basically on a user management.

00:13:28.360 --> 00:13:29.740
Right. So the.

00:13:37.380 --> 00:13:39.820
There are two different audit log site.

00:13:39.940 --> 00:13:42.340
One, what is happening on a cluster?

00:13:42.980 --> 00:13:45.200
The other thing is, who is actually doing.

00:13:47.680 --> 00:13:49.860
Yeah. Yeah. So which one you're checking.

00:13:50.760 --> 00:13:52.020
You want both.

00:13:54.220 --> 00:14:01.580
Maybe like we need to check them like how they do the audit logs, all this stuff we can ask them to get it.

00:14:01.880 --> 00:14:02.280
Generally.

00:14:04.100 --> 00:14:06.360
They have the.

00:14:06.360 --> 00:14:10.380
General logs like what is happening on top of the cluster.

00:14:11.040 --> 00:14:13.500
But if you want to know which user is doing what.

00:14:14.440 --> 00:14:14.760
I'm not.

00:14:16.160 --> 00:14:20.700
You can ask conflict to say, hey, can you give me the user audit law?

00:14:21.680 --> 00:14:23.580
Then probably they may probably.

00:14:25.480 --> 00:14:27.720
But general logs will be audit logic.

00:14:27.760 --> 00:14:29.500
What is happening for a topic?

00:14:29.640 --> 00:14:32.220
What is happening for a cluster?

00:14:32.800 --> 00:14:34.300
Whether modified all the stuff.

00:14:34.300 --> 00:14:38.420
But who is managing it and who is using it?

00:14:38.420 --> 00:14:40.260
Probably they can't forward, but.

00:14:42.900 --> 00:14:50.280
I don't know, like, which plan you're using based on the plan they may have or they may not have it.

00:14:50.460 --> 00:14:51.340
We need to respond.

00:14:54.760 --> 00:15:00.760
Yeah. Based on the plan, they may give you the.

00:15:00.760 --> 00:15:02.860
If you see if you want to really.

00:15:04.040 --> 00:15:05.120
I'm just using this for.

00:15:05.320 --> 00:15:12.300
But if they are using any standard dedicated premium kind of thing, then just definitely they should be having the logs and probably the report.

00:15:14.080 --> 00:15:18.080
So we can ask them to emit them to some our own.

00:15:20.480 --> 00:15:25.940
So with this or the final server, then we can take it kind of give it what is happening and put a lot of.

00:15:26.720 --> 00:15:31.720
Yes, I also want to show how we can do the other things here.

00:15:32.380 --> 00:15:34.460
So let's say in this dashboard.

00:15:36.080 --> 00:15:43.360
OK, if something is going, we want to specifically do some alerting mechanism, like send them a kind of thing.

00:15:43.700 --> 00:15:46.420
So we can do add other tools.

00:15:52.980 --> 00:16:04.840
Saying that what type of data source you select and we want what data or dashboard, then choose what is the point and search something like that and create a rule and add it.

00:16:04.940 --> 00:16:05.280
Let's say.

00:16:07.300 --> 00:16:12.740
Let's say I'm saying this is my data source and I want this metric to be calculated.

00:16:12.740 --> 00:16:14.600
Then click on that.

00:16:14.800 --> 00:16:17.920
Then you get the query and add it.

00:16:18.300 --> 00:16:22.060
And on top of it, you select the room and kind of add it.

00:16:22.540 --> 00:16:25.700
Then do what you want to do with them.

00:16:25.760 --> 00:16:29.340
OK, whether you want to do say between something else or kind of them.

00:16:30.480 --> 00:16:31.040
Then.

00:16:31.300 --> 00:16:35.100
The Fana has its own inbuilt SMTP server.

00:16:35.720 --> 00:16:40.380
You can actually send them a message to any one of the configured units.

00:16:40.980 --> 00:16:42.960
That also can be done on the phone.

00:16:44.180 --> 00:16:51.180
If you are using a phone, it is like a useful alerting mechanism.

00:17:01.720 --> 00:17:06.240
What are we are getting from the confluent dashboard, right?

00:17:06.260 --> 00:17:07.380
Those are very limited.

00:17:08.160 --> 00:17:12.800
But if you still want to go ahead and further dive deep into more matrices.

00:17:14.300 --> 00:17:17.340
This is where you are doing like the document, which I have added right monitoring.

00:17:20.160 --> 00:17:26.000
This emits a lot of matrices like broker matrices, which I have discussed yesterday.

00:17:26.160 --> 00:17:26.880
Some of them.

00:17:27.780 --> 00:17:29.640
And you can put alerts on top of it.

00:17:29.820 --> 00:17:31.120
These are all the brokers are a meter.

00:17:31.260 --> 00:17:35.060
There are a number of matrices, which is like you can check.

00:17:35.340 --> 00:17:35.540
I should.

00:17:35.720 --> 00:17:39.700
I was saying like how we do the batch size, the average batch size max.

00:17:40.840 --> 00:17:45.520
We're using this matrices when you do any performance test.

00:17:46.080 --> 00:17:52.840
By using this matrix, we can increase the batch size, decrease the batch size, and you can select how many partitions you need.

00:17:53.180 --> 00:17:55.100
What's the throughput in general?

00:17:55.300 --> 00:18:03.800
This is what if you're doing any performance testing on the stuff, we use these matrices to manage it.

00:18:04.380 --> 00:18:09.220
You see here we have all the matrices like you asked about this one.

00:18:09.220 --> 00:18:12.440
Probably we can ask them to see what is happening on.

00:18:12.640 --> 00:18:20.340
But this generally what is happening on a high level, but not sure in detail at user level.

00:18:20.500 --> 00:18:22.140
I am not sure.

00:18:22.800 --> 00:18:26.440
In the next session, we will see about the general issues.

00:18:29.640 --> 00:18:34.440
And see how we can mitigate them or how we can.

00:18:35.440 --> 00:18:37.400
Fine tune the cost per service.

00:18:41.080 --> 00:18:44.220
Is everybody able to get the.

00:18:44.900 --> 00:18:46.760
This is what everybody I am seeing.

00:18:47.820 --> 00:18:49.420
Are we good or you still have any issues.

00:18:50.420 --> 00:18:52.440
But, you know, you want to have that.

00:18:57.540 --> 00:18:58.220
Yeah.

00:19:04.360 --> 00:19:10.760
Are you using any kind of these dashboards or you're just using the default.

00:19:15.000 --> 00:19:15.640
Okay.

00:19:16.400 --> 00:19:18.400
They're just maybe like shading on a high level.

00:19:19.720 --> 00:19:21.660
I think there are some metrics like.

00:19:23.940 --> 00:19:25.800
Give me a number.

00:19:26.460 --> 00:19:28.040
You don't show it.

00:19:33.400 --> 00:19:36.680
So actually, there is an user management thing.

00:19:36.680 --> 00:19:37.920
Probably they can and user.

00:19:38.260 --> 00:19:41.160
But if they add user, there is a cost of society.

00:19:41.620 --> 00:19:41.980
So probably.

00:19:46.980 --> 00:19:48.960
Yeah, yeah.

00:19:50.900 --> 00:19:54.040
They should be generally doing it.

00:19:54.060 --> 00:19:56.940
They should be giving you access at least like read only dashboards.

00:19:57.680 --> 00:19:59.000
Maybe the same.

00:19:59.300 --> 00:20:00.360
Yeah, but.

00:20:01.040 --> 00:20:02.240
We want it to be on the same.

00:20:03.780 --> 00:20:05.900
I don't even remember.

00:20:07.640 --> 00:20:09.040
I'm sorry.

00:20:09.040 --> 00:20:09.940
Excuse me.

00:20:17.920 --> 00:20:19.320
Okay.

00:20:21.840 --> 00:20:23.240
Okay.

00:20:24.340 --> 00:20:24.780
Okay.

00:20:31.320 --> 00:20:32.720
Okay.

00:20:32.720 --> 00:20:34.480
Thank you.

00:20:55.760 --> 00:20:57.940
Thank you.

00:21:43.000 --> 00:21:43.060
Thank you.

00:22:13.020 --> 00:22:13.080
Thank you.

00:22:43.020 --> 00:22:43.080
Thank you.

00:23:13.020 --> 00:23:13.080
Thank you.

00:23:43.320 --> 00:23:43.380
Thank you.

00:24:11.680 --> 00:24:12.040
Thank you.

00:24:43.460 --> 00:24:43.520
Thank you.

00:24:57.540 --> 00:24:58.940
Thank you.