95 karma · joined August 11, 2021
About the future: "We posed an open-ended question about what people were most excited about in this space, and it’s clear respondents are keen to see the market’s continued maturation. Some of the top items cited were continued centralization, improved ease of use, and greater data correlation. Several OSS tools also made the list, including OpenTelemetry and Grafana Loki."
1. You can keep (pun intended) the actual alert YAMLs wherever you like, the CLI gets the alert as an argument.
2. If by observe you mean a UI where you can see all your alerts, this is something we're currently working on.
3. In the upcoming days we will also release "deployment" options so you can click-to-production with your alerts.
Would love to help more if you're still struggling
The project aims to provide the following use cases:
1. Declarative alerting that can be managed in your version control and service repository.
2. Alerting from multiple data sources, allowing for more context and enrichments.
3. Elimination of vendor lock-in, making it easier to transition from one observability tool to another.
Additional features we plan to include are:
- Integration with CI/CD processes to facilitate alerts maintenance and coverage.
- Scoring to evaluate the alert's actionability and contextual information.
- Slack integration to track alerts channels over time.
- More providers, conditions, etc
I'm working around an idea of making it easy for SaaS product being deployed with hybrid deployment (mainly around separating control and data).
Would be super cool if you will answer my very simple poll on your SaaS.
Of course this is anonymous poll and you can see the results after submitting the form.
Thanks!
The first ad there which look super legitimate leads to the following link - "https://www.googleadservices.com/pagead/aclk?sa=L&ai=DChcSEw..."
Which in turn redirects to "https://anazon.snop.eechoman.com/primeservices/action.php?ac..." which looks like a phishing page for Amazon Prime.
Does anyone experience the same behaviour? I've almost used my password there. Why the heck does Google allow such ad's?
I would suggest to split this problem into two different problems - the processing ("data in use") vs data on rest. Each of these problems should be tackle with a different solution/approach.
I'm working on the tackling the second approach and if anyone want to talk just reach out (reply/mail/link/whatever you prefer)