Piotr Klubinski comments

Results 26 comments of


                                            Piotr Klubinski

Best strategy to manage > 400 SLOs

I've asked myself same question few days ago. I'm in similar spot (20 microservices, at least 10 SLOs per service). Currently I'm doing POC with helm where I wrap around...

Best strategy to manage > 400 SLOs

In the end I'll most likely end up with both, but currently main focus is on SLO per microservice. Reasoning behind it is that different microservices can have different objectives...

Best strategy to manage > 400 SLOs

Oh, sorry, I guess I misunderstood your question. Where do you deploy your rules? Into kubernetes with operator? Either way i think it's anyways better to keep records with services,...

Best strategy to manage > 400 SLOs

So... If you can, I'd suggest using operators... two of them: sloth and prometheus operator. Then you won't have to store long prometheus rule files, just their definitions, and both...

[Bug]:"Failed to init storage factory","error":"failed to create primary Elasticsearch client: health check timeout: no Elasticsearch node available"

@navin-rai did you enable fine-grained-access on OpenSearch domain? If yes, then proper credentials must be provided, if not, then you can't pass username nor password as environment variables. Another thing...

[Bug]:"Failed to init storage factory","error":"failed to create primary Elasticsearch client: health check timeout: no Elasticsearch node available"

No, that's a completely different mechanism. My PR was not merged yet, so you can't use it yet. What you can do to test your case is remove below lines...