Hello Jean,
I do not know if you can do much about it, but your MUA did incorectly
wrapped the previous lines out its answers, quoting some of you replies
and unquoting some of mine. I found it complicated to read.
Le 15/03/2021 à 15:55, Jean Helou a écrit :
> Hi Benoit,
>
>
>> Regarding
Hi Benoit,
> Regarding Prometheus setup, we have implemented an optional HTTP
> endpoint. I would recommend you to include the following lines in your
> webadmin.properties:
>
> extensions.routes=org.apache.james.webadmin.dropwizard.MetricsRoutes
>
Thanks! I'll have a look.
> We should then:
On Fri, 2021-03-12 at 21:50 +0700, Tellier Benoit wrote:
> Hello Matthieu,
>
> Le 12/03/2021 à 21:14, Matthieu Baechler a écrit :
> > Hi,
> >
> > My answers below.
> >
> > On Thu, 2021-03-11 at 15:17 +0200, Juhan Aasaru wrote:
> > > Hi!
> > >
> > > There is currently ongoing work to upgrade
Hello Matthieu,
Le 12/03/2021 à 21:14, Matthieu Baechler a écrit :
> Hi,
>
> My answers below.
>
> On Thu, 2021-03-11 at 15:17 +0200, Juhan Aasaru wrote:
>> Hi!
>>
>> There is currently ongoing work to upgrade James to Elasticsearch 7.x
>> See https://github.com/apache/james-project/pull/328
>>
Hello Jean,
Regarding Prometheus setup, we have implemented an optional HTTP
endpoint. I would recommend you to include the following lines in your
webadmin.properties:
extensions.routes=org.apache.james.webadmin.dropwizard.MetricsRoutes
We should then:
- better document this setup
- (provide
Hi,
My answers below.
On Thu, 2021-03-11 at 15:17 +0200, Juhan Aasaru wrote:
> 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
>
Hello all,
I agree that ES is not the best tool for metrics but it's implemented,
documented and demonstrated
- https://james.apache.org/server/metrics.html
- https://james.apache.org/server/config-elasticsearch.html
-
+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
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
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
10 matches
Mail list logo
