+1 I am fine with both proposals Maybe the documentation needs to be modified to clearly say it.
Benoit Le 11/03/2021 à 20:34, Juhan Aasaru a écrit : > If the community agrees then I propose the following. > > * we deprecate this functionality in the next release (3.6.0) with a note > that it would be completely removed in the next release (3.7.0) > * this functionality (James storing history of its metrics to > Elasticsearch) would continue to work with Elasticsearch 6 while rest of > the Elasticsearch-related functionality would be upgraded to Elasticsearch 7 > * anyone still using it would have to run two different Elasticsearch > instances (Elasticsearch 6 for history of metrics and Elasticsearch 7 for > rest of James) > > Juhan > > > > Kontakt Juhan Aasaru (<[email protected]>) kirjutas kuupäeval N, 11. märts > 2021 kell 15:17: > >> Hi! >> >> There is currently ongoing work to upgrade James to Elasticsearch 7.x >> See https://github.com/apache/james-project/pull/328 >> >> Current James can be configured to save James metrics to a separate index >> in Elasticsearch. >> And then Grafana dashboards can be configured to display the history of >> these saved metrics. >> For more detailed documentation refer the configuration parameter >> "elasticsearch.metrics.reports.enabled" here: >> https://james.apache.org/server/config-elasticsearch.html >> >> This functionality that gathers and publish metrics is provided by an >> unmaintained library: >> https://github.com/linagora/elasticsearch-metrics-reporter-java >> This library is not compatible with Elasticsearch 7.x >> >> We are proposing to remove this functionality from James as >> the industry standard is to use external tools that are purpose built for >> pulling and storing the metrics. >> >> Users currently relying on this functionality would have to configure some >> monitoring tool (like Prometheus) to regularly pull and store these metrics >> if they want to continue displaying history of various James related >> metrics over time. >> >> Please respond if you agree or are against removing it. >> >> Kind regards >> Juhan Aasaru >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
