+1 I will prepare one for alerts. ----- Original Message ----- > From: "Heiko W.Rupp" <hrupp(a)redhat.com&gt; > To: "Discussions around Hawkular development" <hawkular-dev(a)lists.jboss.org&gt; > Sent: Tuesday, November 10, 2015 8:43:26 AM > Subject: [Hawkular-dev] Version endpoint for components > > Hey, > > I think it would be good for all components that have a REST interface > to have a /version endpoint that responds on GET and which returns > - the tag (e.g. 0.8.1.Final or 0.3.44-SNAPSHOT or 1.2.3-src-dep-0xcafebabe)) > - the git hash they are built from (less needed for .Final) > > So that clients can easily verify what version they have as peer. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev

On 10 Nov 2015, at 11:51, Thomas Segismont wrote: > We have the /status endpoint already in Metrics for this purpose. Yep, that looks pretty good: '{"MetricsService":"STARTING", "Implementation-Version":"0.9.0.Final-SRC-revision-9080fcfbe40a66ce8143c477b 5d6f8fbadeecf3a", "Built-From-Git-SHA1":"9080fcfbe40a66ce8143c477b5d6f8fbadeecf3a"}' We need to make sure that all the components use the same keys, which may either require to add a "status" to the above or to rename the "MetricsService" to "status" or similar. _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev