[
https://issues.apache.org/jira/browse/DISPATCH-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789821#comment-16789821
]
Gordon Sim edited comment on DISPATCH-1278 at 3/11/19 6:15 PM:
---------------------------------------------------------------
To try it out:
1. create config file for router, e.g.
{noformat}
router {
mode: interior
id: Router.A
}
listener {
host: 0.0.0.0
port: amqp
authenticatePeer: no
saslMechanisms: ANONYMOUS
}
listener {
host: 0.0.0.0
port: 8080
http: true
authenticatePeer: no
saslMechanisms: ANONYMOUS
}
{noformat}
2. create config file for prometheus, e.g.
{noformat}
global:
scrape_interval: 15s # By default, scrape targets every 15 seconds.
scrape_configs:
- job_name: router-1
# Override the global default and scrape targets from this job every 5
seconds.
scrape_interval: 5s
metrics_path: /metrics
static_configs:
- targets: ['localhost:8080']
{noformat}
3. run router using config above
4. run prometheus using config above (I did this using docker:)
{noformat}
docker run --network=host -p 9090:9090 -v
$(pwd)/prometheus.yml:/etc/prometheus/prometheus.yml prom/prometheus
{noformat}
Then you can point your browser to prometheus web console
([http://localhost:9090|http://localhost:9090/] in my case) and you should be
able to see the metrics being scraped from the router (which broadly correspond
to those seen from qdstat -g).
was (Author: gsim):
To try it out:
1. create config file for router, e.g.
{noformat}
router {
mode: interior
id: Router.A
}
listener {
host: 0.0.0.0
port: amqp
authenticatePeer: no
saslMechanisms: ANONYMOUS
}
listener {
host: 0.0.0.0
port: 5673
authenticatePeer: no
saslMechanisms: ANONYMOUS
}
listener {
host: 0.0.0.0
port: 8080
http: true
authenticatePeer: no
saslMechanisms: ANONYMOUS
}
{noformat}
2. create config file for prometheus, e.g.
{noformat}
global:
scrape_interval: 15s # By default, scrape targets every 15 seconds.
scrape_configs:
- job_name: router-1
# Override the global default and scrape targets from this job every 5
seconds.
scrape_interval: 5s
metrics_path: /metrics
static_configs:
- targets: ['localhost:8080']
{noformat}
3. run router using config above
4. run prometheus using config above (I did this using docker:)
{noformat}
docker run --network=host -p 9090:9090 -v
$(pwd)/prometheus.yml:/etc/prometheus/prometheus.yml prom/prometheus
{noformat}
Then you can point your browser to prometheus web console
([http://localhost:9090|http://localhost:9090/] in my case) and you should be
able to see the metrics being scraped from the router (which broadly correspond
to those seen from qdstat -g).
> Add support for prometheus metrics export
> -----------------------------------------
>
> Key: DISPATCH-1278
> URL: https://issues.apache.org/jira/browse/DISPATCH-1278
> Project: Qpid Dispatch
> Issue Type: New Feature
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Priority: Major
> Fix For: 1.6.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]