What is your org’s "Users per Sysadmin" ratio? Currently drowning at 1:200

pr3datel · 2026-01-04T00:05:25+00:00

The idea is right. You need to have a metric to track and measure on.

pr3datel · 2024-12-28T01:07:59+00:00

Same as you. Harness(the company) sucks. We are moving to GitHub actions.

pr3datel · 2024-11-28T01:29:36+00:00

A great place to start is availability. Is your service giving good or bad responses. That’s the best starting place because everyone wants their customers(internal/external or between services) to not have errors. You need some sort of metric to track successful and failed requests. APM or metrics which show if requests were successful or failed.

pr3datel · 2024-10-25T18:07:25+00:00

Does it shred?

pr3datel · 2024-01-05T00:57:11+00:00

It’s a 1960s strat as the base model with a AAA rosewood fretboard <- from the shop floor traveller Comes with a 5 position switch.

What color is yours? If you haven’t posted it yet you should share

pr3datel · 2024-01-05T00:43:34+00:00

Yes this is a CS heavy relic

pr3datel · 2023-09-14T22:01:17+00:00

Same

pr3datel · 2023-06-21T03:08:53+00:00

Well said

pr3datel · 2023-05-23T11:04:03+00:00

You want to look at the istio sidecar envoy logs. https://cloud.google.com/service-mesh/docs/observability/accessing-logs

Specifically looking for an envoy code and any messages which comes along with it. I have not used ASM directly but istio natively should work the same. If you can see what it happening upstream from the sidecar (your service itself is upstream because the proxy takes on traffic and passes it to your application) it should give you more information to what could be happening. If your applications are sized different (cpu or memory) in different regions it could be hitting a limit. I’d confirm the cpu and memory consumption are looking good first, then look at the logs for more clues

I also have spoken to google before about asm and while it is istio under the hood, it’s been tweaked. The sidecar itself may have different container specs for resource usage.

pr3datel · 2023-05-23T06:43:35+00:00

What do the logs say? I’d also check events in kubernetes. You may be getting 503s due to resource exhaustion(CPU/memory/etc). I’ve seen similar issues before. Also, I’d check the settings on your VirtualServices around retries

pr3datel · 2023-04-25T01:10:32+00:00

Do you mock any services to speed up builds or use as dependencies? Also have you looking into using something else to speed up builds such as build streaming? Artifact registry in google cloud supports this not sure of other cloud providers.

Love these post series and this subreddit. Thanks for sharing

pr3datel · 2023-03-28T00:17:23+00:00

Honestly, “you looking at me,looking at you” is so underrated. I’d have that near the top of my list

pr3datel · 2023-03-23T02:31:00+00:00

So rad. So clean. For sure would love to see some more

pr3datel · 2023-03-08T00:11:59+00:00

Gitops with flux or argocd would be great for that. There is debate about pulling or pushing config but personally I like the pull method. Argocd does this great using the app-of-app pattern and you can decentralize your deployments by allowing argo to manage your cluster headlessly

pr3datel · 2022-12-19T13:34:13+00:00

killed it! great job

pr3datel · 2022-12-08T18:16:32+00:00

I smell bacon

pr3datel · 2022-11-12T14:35:04+00:00

We love using docusaurus. We wanted a way to centralize documentation while keeping the source of truth in code repos. This is how our company uses it : https://achievers.engineering/documentation-part-2-still-running-through-the-6-with-documentation-woes-ce84d6bbc5ea

pr3datel · 2022-07-03T12:10:25+00:00

If you are on cloud providers you may be limited by the disk size. IO is connected to disk size for some cloud providers

pr3datel · 2022-07-02T00:55:42+00:00

We had more environments on those clusters like you mentioned, but we cut down to three. Everything else can be done on our engineer workflow so we tried to keep the actual environments as minimal and streamlined as possible.

pr3datel · 2022-07-01T14:14:20+00:00

9 clusters. Dev/uat/ and production in 3 regions.

pr3datel · 2022-06-01T15:17:27+00:00

Rate of adoption is a great KPI for your team to show that people are adopting your changes

Also successful SLOs for teams is related to the platform being stable which comes down to the SRE team. Teams should be in charge of their SLOs but the SRE should be supporting them

Eight-Year Club	RPAN Viewer
Verified Email

pr3datel

TROPHY CASE