Monitoring, logging, alerting, ci/cd, automation of the creation of resources about chapter HOT 12 CLOSED

Also for elastic what is the scope of usage? will there be a need for multiple indexes?

from chapter.

All of this makes sense if you're providing a managed service, but I was just reading through the readme and it seems like the output of this project (for now) will be a Docker container that you can run on your own infrastructure.

If the goal is to have one-click deployment, I would think that the short term goals would be to create deployment scripts/templates that can deploy this to AWS, Google Cloud, Microsoft Azure, Heroku, Linode, etc.

As an community organizer, two things that are important to me are:

• Ease of use (i.e. easy to run and maintain)
• Low cost to operate

While it's not an issue for me to run a docker container on a virtual server somewhere, something like Google's Cloud Run or AWS's ability to launch CloudFormation templates would probably make it easier for users to deploy the software with fewer steps.

from chapter.

I vote elastic stack for reporting and monitering

from chapter.

I vote for this ( https://github.blog/2019-08-08-github-actions-now-supports-ci-cd/ ) regarding CI/CD. It is free for public repo. 😄

from chapter.

Prometheus for monitoring?

from chapter.

@jeremiahlukus Please do go into a little more detail for us non-devops peeps. I'm not familiar with some of the names you mentioned there. Would be good trip know what reach one does and why you'd use it.

from chapter.

Why not VSTS ? we can make practically everything there CI/CD ...
https://azure.microsoft.com/pt-br/services/devops/

from chapter.

If someone is looking to attract more of the CI folks with the related skills for this feature then we've been logging the various skills from people in the Discord channel. Also, folks are posting directly on the Github thread.

So, see the list of volunteers and skills at search for "circleci" and related terms. The page is long so you may need to un-collapse some parts of the thread.

#11 (comment)
and try to connect with them as needed.

from chapter.

+1 for GitHub Actions, use it for a few things and it's great!

from chapter.

I vote elastic stack for reporting and monitering

Note that the official alerting functionality, and all but basic monitoring features for the Elastic stack are platinum (paid-for) feature, so we should look for other solutions. The free tier of the Elastic stack is still great for logging.

Alongside the free tier of the Elastic stack, I use Grafana for certain types of alerts like thresholds (and in preference to Kibana for creating most of my graphs), and Yelp's ElastAlert for any types of alerting that Grafana doesn't support.

Note: I won't say that ElastAlert is a pleasure to use. But it's one approach that doesn't cost anything.

from chapter.

@shirakaba Also keep in mind splunk also has a free option:

Splunk® Free
One User
Scale up to 500 MB data per day
Collect and index any machine data
Real-time search and analysis

One problem is that we only get 1 user but if we set it up correctly as an admin account we might be able to make it work in our distributed system

from chapter.

We will consider adding some tools like this once we have shipped our MVP. For now I'm closing this stale issue.

from chapter.