Open Justus-at-Tazama opened 1 year ago
We have reasonable experience and understanding of the requirement for logging out of the platform and have done quite a bit of work to improve the functionality around logging, implementing things like variable log-levels across the platform and even the ability to disable logging altogether.
Our problem is that our current approach consumes overwhelming resources, to the point where we may not recommend that it is enabled in a production setting.
Question: Is ELK still the right solution? Can we use something like OpenTelemetry, Sentry or Prometheus?
The [Elastic License 2.0](https://www.elastic.co/licensing/elastic-license) applies to our distribution and the source code of all of the free and paid features of Elasticsearch and Kibana. Our goal with ELv2 is to be as permissive as possible, while protecting against abuse. The license allows the free right to use, modify, create derivative works, and redistribute, with three simple limitations:
- You may not provide the products to others as a managed service
- You may not circumvent the license key functionality or remove/obscure features protected by license keys
- You may not remove or obscure any licensing, copyright, or other notices
e.g. I provide Elasticsearch and Kibana as a service, where my customers have direct access to substantial portions of the Elasticsearch APIs and Kibana UI.
This use is not permitted under the ELv2. Please reach out to us to discuss your options.
https://logit.io/blog/post/open-source-logging-tools/ https://logit.io/blog/post/splunk-alternatives-competitors/
Story statement
As a [the beneficiary of this feature], I want [what does the beneficiary want to be able to do?], So that [what is the benefit or value of the feature?] And so that [list ALL the benefits, one at a time]
Acceptance criteria