WEBVTT 00:00.060 --> 00:00.270 Okay. 00:00.360 --> 00:04.830 So I'm not going to set up a low key data source on microphone, a cloud instance. 00:04.980 --> 00:10.410 If we look at what was created early on in the course where I set out to file a server manually, I 00:10.410 --> 00:16.800 set up a low key data source where I pointed it to a low key service running on the same service microphone, 00:16.800 --> 00:17.210 a server. 00:17.220 --> 00:22.290 I then also installed a prompt mail service which was also on the same server and that was collecting 00:22.290 --> 00:28.200 logs and through the low key data source upon a user device, I could query that data being gathered 00:28.210 --> 00:29.010 by pronto. 00:29.070 --> 00:31.860 So when setting this up on the cloud, it's slightly different. 00:31.860 --> 00:36.990 This is my cloud instance of Carafano as zero s big kind of fun about it. 00:37.020 --> 00:42.150 I'm going to set up the low key data source and it will give me a URL that I can push data to. 00:42.150 --> 00:47.640 So with the prompt mail service just running on my existing graph on a server, I'll reconfigure it 00:47.670 --> 00:51.720 to point directly to my cloud hosted Gravano instance instead. 00:51.720 --> 00:55.680 So the difference here is, instead of manually installing a low key service on microphone or server 00:55.680 --> 00:58.440 or somewhere the microphone a server can access. 00:58.440 --> 01:04.320 I'm now using the low key data source that I'll configure inside microphone a cloud instance though 01:04.330 --> 01:06.420 prompt I will instead send to that one. 01:06.420 --> 01:13.980 So back into your gryphon our account on Gryphon a dot com here low key click the details in your information 01:13.980 --> 01:15.210 of course will be different to mine. 01:15.210 --> 01:19.170 But anyway, I need to create an API key, so generate that. 01:19.170 --> 01:22.230 Now the key will be used to push data the low key. 01:22.230 --> 01:23.450 So anything you like. 01:23.460 --> 01:29.310 So prom tale publisher seems like a good one for me and the role as a matrix publisher you can add many 01:29.310 --> 01:29.640 people like. 01:29.670 --> 01:30.870 So I create the API key. 01:30.870 --> 01:31.590 Okay, that's done. 01:31.590 --> 01:35.730 Now I'm going to change this after the video so it will be different and also your key will be different 01:35.730 --> 01:36.020 as well. 01:36.030 --> 01:40.560 Don't share that this is a secret that you shouldn't really share with anyone but may change mine after 01:40.560 --> 01:41.250 this video is over. 01:41.260 --> 01:42.270 So it's a different one. 01:42.270 --> 01:43.860 You can delete them and create new ones. 01:44.040 --> 01:45.780 I close that anyway. 01:45.780 --> 01:48.540 Scrolling down sending logs from a standalone host. 01:48.540 --> 01:50.160 This is referring to prompt mail. 01:50.310 --> 01:56.160 You go into your prompter config and you add a URL being in the form of that. 01:56.250 --> 02:02.790 So on this diagram, I'm going to edit my prompter configuration with that long URL, which points to 02:02.790 --> 02:03.120 that. 02:03.180 --> 02:03.450 Okay. 02:03.450 --> 02:07.980 So I switched onto my server where I've got my existing location prompt or running and happens to be 02:07.980 --> 02:11.250 my always this version of command that I've created early on in the course. 02:11.250 --> 02:13.500 But anyway, I'm just going to modify the prompt. 02:13.500 --> 02:18.210 I'll remember when we install the prompt, our binary, we installed it into the user local bin folder. 02:18.210 --> 02:22.830 So I'm going to go back to their a city's local bin and just look at that okay. 02:22.860 --> 02:24.880 Says config from tell why email. 02:24.900 --> 02:26.340 I'm going to edit that so. 02:27.770 --> 02:34.940 Config run tail wire now and all the settings are good, except this URL is no longer pointing to a 02:34.940 --> 02:37.460 local version of Loki, so I'm going to delete that. 02:38.060 --> 02:45.160 But through this new URL here which contains my key I just generated plus the full URL. 02:45.170 --> 02:46.550 So just copy that. 02:46.550 --> 02:51.650 And in from tail here if you right click it will paste that whole line in. 02:51.650 --> 02:52.720 So that's it. 02:52.730 --> 02:54.110 There's quite a long line. 02:56.450 --> 02:57.620 That is good. 02:57.650 --> 03:00.680 So control X to say yes. 03:00.800 --> 03:02.700 Now you should restart from tail. 03:02.720 --> 03:06.000 But first I'm just going to double check that in microphone, for instance. 03:06.080 --> 03:07.770 So microphone, a cloud instance here. 03:07.790 --> 03:12.340 Down in data sources given a cloud is be code logs click that. 03:12.350 --> 03:18.020 And if we look at it the basic auth details being the user and the password is already configured. 03:18.050 --> 03:19.730 This was created automatically. 03:20.090 --> 03:24.620 As it says here, this data source was added by config and cannot be modified in the UI. 03:24.650 --> 03:25.610 So it's already good. 03:26.160 --> 03:29.300 So I can even test that and just testing. 03:30.220 --> 03:30.440 Okay. 03:30.460 --> 03:34.930 Data source connected and labels fan, but there's actually no data in there yet because I haven't actually 03:34.930 --> 03:36.820 restarted that prompter server. 03:36.820 --> 03:38.980 So to send to that endpoint just yet. 03:38.980 --> 03:39.910 But we'll do that now. 03:39.910 --> 03:40.870 So Sudo. 03:41.900 --> 03:48.890 Service from title restart with ticket status. 03:49.960 --> 03:51.620 It's looking good so far. 03:51.930 --> 03:52.310 Okay. 03:52.460 --> 03:53.630 Traverse City, Red Alert. 03:54.530 --> 03:57.830 If I go to explore the. 03:59.250 --> 04:05.910 And select ESP Code Logs, Click Log browser and it's already showing me those labels that I've set 04:05.910 --> 04:06.150 up. 04:06.150 --> 04:10.770 So this auth log in those syslog, these were things set up in the course earlier on. 04:10.890 --> 04:13.830 So let's look at var logs and show logs. 04:14.640 --> 04:15.900 Log volume is loading. 04:15.930 --> 04:17.820 Now we go and there's a whole lot of information. 04:18.030 --> 04:23.700 Okay, so remember we've looked a lot at from Tile and Loki earlier in the course, so you can do all 04:23.700 --> 04:25.950 those things now throughout your cloud instance. 04:26.160 --> 04:26.350 Okay. 04:26.430 --> 04:30.260 So looking at that image again, I've re pointed that from tile to look at that and state. 04:30.280 --> 04:33.750 So I'm no longer using that Gryphon server I've installed there. 04:33.750 --> 04:38.310 Now also if you have another prompt our service running somewhere else, it's the same process. 04:38.310 --> 04:43.710 That URL that I got from the settings screen, I put that in that from tile service and restarted as 04:43.710 --> 04:48.680 well and I can have multiple rom tiles all pushing to my Loki data source lock. 04:48.720 --> 04:53.820 So I'm not going to do that at the moment because I'm still not fully aware of whether that will take 04:53.820 --> 04:55.380 me over the free allows for or not. 04:55.380 --> 05:01.050 These are things that you should keep an eye on, but you can always go to your profile, the default 05:01.050 --> 05:06.750 page there and you'll see that the logs information should increment over time. 05:06.750 --> 05:10.230 You want to make sure you don't go above 50 gigabytes in one month. 05:10.230 --> 05:13.440 So just be careful that if you're worried about spending extra money. 05:13.470 --> 05:13.870 Okay. 05:13.890 --> 05:20.430 And looking at the data sources again for Loki, ESB code logs, we can look at insights and there's 05:20.430 --> 05:25.200 nothing to see here just yet, but we'll start to see these graphs update and that will give us a good 05:25.200 --> 05:27.420 indication of whether we're going over the free limit or not. 05:27.420 --> 05:27.870 Excellent. 05:27.930 --> 05:33.150 The next video was set up by Matthias service to push to my on a cloud instance. 05:33.150 --> 05:33.600 Excellent.