Okay.
So I'm not going to set up a low key data source on microphone, a cloud instance.
If we look at what was created early on in the course where I set out to file a server manually, I
set up a low key data source where I pointed it to a low key service running on the same service microphone,
a server.
I then also installed a prompt mail service which was also on the same server and that was collecting
logs and through the low key data source upon a user device, I could query that data being gathered
by pronto.
So when setting this up on the cloud, it's slightly different.
This is my cloud instance of Carafano as zero s big kind of fun about it.
I'm going to set up the low key data source and it will give me a URL that I can push data to.
So with the prompt mail service just running on my existing graph on a server, I'll reconfigure it
to point directly to my cloud hosted Gravano instance instead.
So the difference here is, instead of manually installing a low key service on microphone or server
or somewhere the microphone a server can access.
I'm now using the low key data source that I'll configure inside microphone a cloud instance though
prompt I will instead send to that one.
So back into your gryphon our account on Gryphon a dot com here low key click the details in your information
of course will be different to mine.
But anyway, I need to create an API key, so generate that.
Now the key will be used to push data the low key.
So anything you like.
So prom tale publisher seems like a good one for me and the role as a matrix publisher you can add many
people like.
So I create the API key.
Okay, that's done.
Now I'm going to change this after the video so it will be different and also your key will be different
as well.
Don't share that this is a secret that you shouldn't really share with anyone but may change mine after
this video is over.
So it's a different one.
You can delete them and create new ones.
I close that anyway.
Scrolling down sending logs from a standalone host.
This is referring to prompt mail.
You go into your prompter config and you add a URL being in the form of that.
So on this diagram, I'm going to edit my prompter configuration with that long URL, which points to
that.
Okay.
So I switched onto my server where I've got my existing location prompt or running and happens to be
my always this version of command that I've created early on in the course.
But anyway, I'm just going to modify the prompt.
I'll remember when we install the prompt, our binary, we installed it into the user local bin folder.
So I'm going to go back to their a city's local bin and just look at that okay.
Says config from tell why email.
I'm going to edit that so.
Config run tail wire now and all the settings are good, except this URL is no longer pointing to a
local version of Loki, so I'm going to delete that.
But through this new URL here which contains my key I just generated plus the full URL.
So just copy that.
And in from tail here if you right click it will paste that whole line in.
So that's it.
There's quite a long line.
That is good.
So control X to say yes.
Now you should restart from tail.
But first I'm just going to double check that in microphone, for instance.
So microphone, a cloud instance here.
Down in data sources given a cloud is be code logs click that.
And if we look at it the basic auth details being the user and the password is already configured.
This was created automatically.
As it says here, this data source was added by config and cannot be modified in the UI.
So it's already good.
So I can even test that and just testing.
Okay.
Data source connected and labels fan, but there's actually no data in there yet because I haven't actually
restarted that prompter server.
So to send to that endpoint just yet.
But we'll do that now.
So Sudo.
Service from title restart with ticket status.
It's looking good so far.
Okay.
Traverse City, Red Alert.
If I go to explore the.
And select ESP Code Logs, Click Log browser and it's already showing me those labels that I've set
up.
So this auth log in those syslog, these were things set up in the course earlier on.
So let's look at var logs and show logs.
Log volume is loading.
Now we go and there's a whole lot of information.
Okay, so remember we've looked a lot at from Tile and Loki earlier in the course, so you can do all
those things now throughout your cloud instance.
Okay.
So looking at that image again, I've re pointed that from tile to look at that and state.
So I'm no longer using that Gryphon server I've installed there.
Now also if you have another prompt our service running somewhere else, it's the same process.
That URL that I got from the settings screen, I put that in that from tile service and restarted as
well and I can have multiple rom tiles all pushing to my Loki data source lock.
So I'm not going to do that at the moment because I'm still not fully aware of whether that will take
me over the free allows for or not.
These are things that you should keep an eye on, but you can always go to your profile, the default
page there and you'll see that the logs information should increment over time.
You want to make sure you don't go above 50 gigabytes in one month.
So just be careful that if you're worried about spending extra money.
Okay.
And looking at the data sources again for Loki, ESB code logs, we can look at insights and there's
nothing to see here just yet, but we'll start to see these graphs update and that will give us a good
indication of whether we're going over the free limit or not.
Excellent.
The next video was set up by Matthias service to push to my on a cloud instance.
Excellent.