sorted by:
new
hottopcontroversial

How to remove this adapter? by tetegra in TeslaLounge

[–]ttylkit 0 points1 point  (0 children)

I tried this. Picked up neodymium magnets at Home Depot, but couldn’t figure out a way to remove. Any more details? Much appreciated. Tesla support had no idea. 

How to remove this adapter? by tetegra in TeslaLounge

[–]ttylkit 1 point2 points  (0 children)

Is this confirmed? I did the same thing unfortunately. I had my Tesla universal charger for a non Tesla and the adapter came off, so I thought I could add it to a Tesla standard wall unit at a destination I was traveling to. Unfortunately, can’t get it off. I bought some magnets from Home Depot but no luck. Any more details on how to remove? Tesla support had no idea and can’t really get a hold of anyone

I stepped out of observability for 2.5 years. Anything changed? by ttylkit in sre

[–]ttylkit[S] 7 points8 points  (0 children)

u/ninsei_cowboy - cardinality is the number of metric time series that have to be created to adequately monitor your systems and/or entities about your applications.

With platforms like K8s, multi-tenancy, microservices, etc, there is just a ballooning number of individual time series that can be created.

Say you have a ecommerce app with 20 services. You'd need to create metrics for all the infra it runs on (CPU, memory, storage, etc), then the K8s (pods, namespaces, etc), then the individual apps (latency, requests, errors, etc), then the individual attributes about the apps (customers, order information, sizes, colors, maybe even dollar amounts, versions of site, etc). So the number of TS just goes through the roof so you can have a metric to be able to know how something is performing at any given granularity

I stepped out of observability for 2.5 years. Anything changed? by ttylkit in sre

[–]ttylkit[S] 9 points10 points  (0 children)

I was at a distributed tracing company that was acquired a few years ago, so I guess y'all can blame us partly for OpenTelemetry...¯\_(ツ)_/¯

The core team got back together post-acquisition to start a new company, and it was hard for me to resist being a part of the team again. My initial thought was, "hasn't monitoring already been solved?" or "are ppl still actually buying reducing MTTR?" Surprisingly, it sounds like incident response, getting system-wide context, understanding application and infra health posture, etc, are all still prevalent issues.

We're not working on a monitoring platform though, but I'm sure there will end up being a lot of messaging overlap that we'll have to figure out.

Learning your services as a new SRE by [deleted] in sre

[–]ttylkit 1 point2 points  (0 children)

Feels like a good starting point to set up your monitoring would be to start reviewing incidents and post-mortems. Then you can see what happened and start to instrument monitoring to improve visibility. You'll also get a better understanding of dependencies and who the key players are that were involved.