Hi Sean ! Let's take a working example:
I have a spring boot web app integrating micrometer/prometheus metrics running on port 8080 : http://webapp:8080. Since it integrates micrometer/prometheus metrics, it exposes a http://webapp:8080/actuator/prometheus endpoint. Then I have a prometheus server (lets say http://prom:9090) whose config is: - job_name: 'prometheus' # metrics_path defaults to '/metrics' # scheme defaults to 'http'. static_configs: - targets: ['prom:9090'] - job_name: 'webapp-actuator' metrics_path: '/actuator/prometheus' scrape_interval: 5s static_configs: - targets: ['webapp:8080'] Therefore, when I got to http://prom:9090/targets, I see two targets : Http://prom:9090/metrics AND http://webapp:8080/actuator/prometheus I would like to configure a third target for Fuseki, given fuseki's prometheus endpoint. it woul lokk like this: - job_name: 'fuseki metrics' metrics_path: '/FUSEKI/EXPOSED/PROMETHEUS_ENDPOINT' scrape_interval: 5s static_configs: - targets: ['FusekiSever:port'] so I would see a third target in the list: http://FusekiSever:port/FUSEKI/EXPOSED/PROMETHEUS_ENDPOINT Am I clear enough and do you see what I am asking for ? (i.e the actual FUSEKI/EXPOSED/PROMETHEUS_ENDPOINT on a Jena FUSEKI server and the way to activate it, if needed) Marc On 2019/10/02 14:29:15, Sean Ryan <ryan.s...@gmail.com> wrote: > You should be able to configure prometheus with something like this (I > think this is what you're asking for?) > > - job_name: 'fuseki' > scrape_interval: 5s > metrics_path: '/$/metrics' > static_configs: > - targets: ['prometheusserver:port'] > > On Wed, Oct 2, 2019 at 3:03 PM Marc Agate <agate.m...@gmail.com> wrote: > > > Hi Sean, > > > > Thanks for the reply. > > > > My concern is to have Fuseki metrics endpoint (for prometheus to scrape > > data) available in the list of prometheus target, here > > (http://prometheusserver:port/targets). > > > > I do have a bunch of metrics listed at > > "http://prometheusserver:port/targets";, > > but none of them pertains to Fuseki Server since fuseki server is not a > > target for prometheus > > > > I would like some Fuseki endpoint available for prometheus, the same way > > we have the "/actuator/prometheus" endpoint available for Spring boot web > > apps. What is the target endpoint for Fuseki Server? > > > > Any clue? > > > > Thanks > > > > On 2019/10/02 13:44:51, Sean Ryan <ryan.s...@gmail.com> wrote: > > > Hi Marc, > > > > > > it should be enabled by default and available at /$/metrics/ > > > > > > What gets exposed are a bunch of the micrometer instrumentations like > > file > > > descriptor, classloading, jvm stuff. See here > > > < > > https://github.com/apache/jena/blob/master/jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/metrics/prometheus/PrometheusMetricsProvider.java#L48-L60 > > > > > > for which ones. > > > > > > There are a couple of other things instrumented just for fuseki... just > > the > > > same stuff as you can see at /$/stats/ (I tihnk is the endpoint) but in a > > > prometheus consumable format > > > > > > I was using this dashboard <https://grafana.com/grafana/dashboards/3308> > > to > > > visualise the micrometer sutff if I remember correctly > > > > > > I don't think this has made it into the latest docker image yet > > > <https://hub.docker.com/r/stain/jena-fuseki> (in case this is how you're > > > using fuseki) > > > > > > Sean > > > > > > On 2019/10/02 12:27:56, Marc Agate <a...@gmail.com> wrote: > > > > Hi all,> > > > > > > > > I am currently monitoring several web services using prometheus and > > > grafana and I would like to integrate our Fuseki server in this > > monitoring > > > system, using > > > org.apache.jena.fuseki.metrics.prometheus.PrometheusMetricsProvider .> > > > > > > > > Does anyone know how to configure this part of Jena Fseki so the Fuseki > > > server expose data to be scraped by prometheus server? Is there any > > > documentation you can point me to?> > > > > > > > > Thanks> > > > > > > > > Marc> > > > > > > > > > >
