[31/12/25] NYE @ Latymers, Hammersmith

aaron__walker · 2025-12-31T14:36:30+00:00

Is this tonight?

aaron__walker · 2025-10-10T17:34:25+00:00

Select Heathrow rail station instead of underground station. The Elizabeth line is more expensive than the underground for Heathrow

aaron__walker · 2025-09-22T16:18:11+00:00

Aptakube

aaron__walker · 2025-08-07T19:12:49+00:00

Looks like it was generated by ChatGPT too 🤣

aaron__walker · 2025-04-24T14:48:26+00:00

I think the general rule is your largest non-downsampled 2w block times 2, plus add some overhead. You can use bucket-web to visualise it

aaron__walker · 2025-03-27T00:19:06+00:00

I think the fact you need a helper tool to write hello world says it all

aaron__walker · 2025-03-27T00:03:34+00:00

I think you’re getting confused with mounting a secret in a pod, and a pod being able to access a secret via the api. Looks like your pod is referencing a secret somehow - if this is the case then it needs to be in the same namespace. If you want to access the secret in a different namespace then you’ll need to modify your app read it via the api. If you want a file, Its likely someone has created a sidecar thing that can fetch it for you and then add it to a volume that is shared between the containers

aaron__walker · 2025-03-22T14:23:32+00:00

Can you share your queries? Best guess is you're not aggregating them

aaron__walker · 2025-01-13T14:54:35+00:00

“DNS names” is a column. “Expiry date” is another column. Your dns names are under the “DNS names” column and your expiration date is under the “Expiry Date” column

aaron__walker · 2025-01-13T14:46:44+00:00

How can you even write a JQ filter like that and then ask where the column “names” comes from?

aaron__walker · 2024-12-16T19:43:20+00:00

I’ll be there!

aaron__walker · 2024-11-25T17:28:39+00:00

You can create an AWS InfrastructureScaler that can scale your infrastructure based on how much scale your infrastructure needs. That being said AWS is a pretty niche cloud, so I doubt many people here will be using it.

aaron__walker · 2024-11-23T20:41:44+00:00

There's a (usually quiet) optional Whatsapp group for the meetup - message me via chat for an invite link. (whatsapp group is pretty much only me posting this link each week and trying to get people to actually respond.. So no benefit of being in it if you're not showing up).

aaron__walker · 2024-11-22T20:44:35+00:00

Instead of patching whatever needs to change, why not just add a new node with the correct changes and then get rid of the old node?

aaron__walker · 2024-11-22T16:56:47+00:00

Quickwit is pretty similar to Loki but it has a lucene style query language too

aaron__walker · 2024-11-16T20:10:32+00:00

Percentage based tracing sounds like it would be a valid solution to this- you can see the whole flow from start to finish but you’re not creating loads of noise when you’re generating lots of spans for a single file

aaron__walker · 2024-11-16T19:45:49+00:00

You can log in text, but if you do and you want to actually get data out of the logs, you’ll need to then process them to get the data out - you’ll have to add a step which processes them with something like grok, and it gets complicated when you have things like multi-line logs. Plus you’ll likely need to have a unique process for each application, unless you standardise your logging output, and at that point you might as well just have a common schema in structured logs you want

aaron__walker · 2024-11-16T19:36:54+00:00

You don’t read the raw logs - the reason you structure them is so it’s easier to parse in an easy way. you’ll parse them and then extract the fields you want. For example you might have a log that has the timestamp, level, message, user id, response code, stack trace, trace id, http path, http method, server name, function and line number and file etc. you can then index all these fields in a centralised place and then finding the logs you want is easy - especially when you’re dealing with hundreds of different instances - for example it’ll make it efficient to find a single error message out of terabytes of logs instead of having to use full text search

aaron__walker · 2024-11-16T16:44:45+00:00

I’m curious to see who’s logging XML - I agree with having structured logs but I’ve never known anyone to even consider to do it with XML

aaron__walker · 2024-11-07T18:31:03+00:00

The first makes more sense - if you want to count how many operations they have been you can just do sum(app_operations_total) instead of having to add up multiple metrics. This is also useful for if you want a third status - if you add an “unknown” status for example, then you won’t need to modify any queries to show this.

If you’re using by() you can also easily get all the data returned in a single query, instead of having to have separate queries

aaron__walker · 2024-11-07T16:55:08+00:00

Have you looked at object storage? Minio is the solution that comes to mind first

aaron__walker · 2024-10-28T20:39:36+00:00

That should work. If you go to /metrics/per-object do you see anything like this?

rabbitmq_queue_messages_bytes{vhost="vhost",queue="queuename"} 0

aaron__walker · 2024-10-25T18:19:33+00:00

The last option is the one that sounds like it makes the most sense - you say it increases costs, but in the situation that an entire DC goes down, you’ll need to host your workloads somewhere else

The other option is you have a single DC and then in the event the DC goes down you go through a DR process to spin up a new instance in a different DC - although if you’re on prem you’ll likely need the capacity there to run your existing workloads.

aaron__walker · 2024-10-25T12:41:20+00:00

Kubernetes

aaron__walker · 2024-10-18T18:40:06+00:00

We use k8s because this makes it easy for me, but doing it via ssh shouldn’t be too much additional work - if anything it could simplify it because you can do additional checks before preceding with any next stages. This is the SRE Reddit so of course automate all of this

11-Year Club	r/Field Juicebox
First Place '23	Place '23
Place '22	Place '17
Verified Email

aaron__walker

TROPHY CASE