-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jira-prometheus-exporter add-on not export *jira* matrics in datacenter mode #61
Comments
Please provide jira version
Also please check log file
чт, 30 янв. 2020 г. в 00:15, agentchif <[email protected]>:
i installed the add-on on Jira DC that contain 2 nodes and 1 Load balancer
in front (haproxy).
i configure the prometheus config.yaml to scrape both nodes and put also
labels on each node.
the scrape section at the prometheus config.yaml look like:
- job_name: 'jira'
scheme: http
metrics_path: '/plugins/servlet/prometheus/metrics'
static_config:
- targets: ['145.1.45.141:8080']
labels:
nodeID: node01
ip: '145.1.45.141'
- targets: ['145.1.45.142:8080']
labels:
nodeID: node02
ip: '145.1.45.142'
the metrics that the exporter export to the prometheus are only jvm &
process TYPES
*there is no JIRA type at all*
hence i cant measure metrics that related to jira like:
jira_issue_update_count
jira_user_login_count
jira_user_logout_count
etc....
anything that start with jira_
BTW,
i have the same configuration at bitbucket and there the bitbucket
exporter is exporting bitbucket metrics include jvm & process
please assist here
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#61?email_source=notifications&email_token=AAPXM4CN7HIKGSKN7ON72T3RAKEANA5CNFSM4KNRUXY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IJYGXSQ>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPXM4BHBJKWUHXPU7BLA73RAKEANANCNFSM4KNRUXYQ>
.
--
*-- Andrey Markelov*
|
Jira Software 7.13.0 (Datacenter) from /var/atlassian/application-data/jira/log/atlassian-jira.log i can see this error: at ru.andreymarkelov.atlas.plugins.promjiraexporter.service.MetricCollectorImpl.licenseMetrics(MetricCollectorImpl.java:435) |
here is a full part of atlassian-jira.log. 2020-01-30 13:02:17,181 localq-stats-0 INFO [c.a.j.c.distribution.localq.LocalQCacheManager] [scheduled] Running cache replication queue stats for: 10 queues... |
I will try to fix it again
On some instances happens on some nope
чт, 30 янв. 2020 г. в 01:08, agentchif <[email protected]>:
Jira Software 7.13.0 (Datacenter)
JIrar Core 7.13.0
from /var/atlassian/application-data/jira/log/atlassian-jira.log i can see
this error:
at
ru.andreymarkelov.atlas.plugins.promjiraexporter.service.MetricCollectorImpl.licenseMetrics(MetricCollectorImpl.java:435)
at
ru.andreymarkelov.atlas.plugins.promjiraexporter.service.MetricCollectorImpl.collectInternal(MetricCollectorImpl.java:489)
at
ru.andreymarkelov.atlas.plugins.promjiraexporter.service.MetricCollectorImpl.collect(MetricCollectorImpl.java:641)
at
io.prometheus.client.exporter.common.TextFormat.write004(TextFormat.java:22)
at
ru.andreymarkelov.atlas.plugins.promjiraexporter.servlet.PrometheusExporter.doGet(PrometheusExporter.java:44)
at
ru.andreymarkelov.atlas.plugins.promjiraexporter.servlet.AllEndpointFilter$1.run(AllEndpointFilter.java:44)
at
ru.andreymarkelov.atlas.plugins.promjiraexporter.service.MetricCollectorImpl.requestDuration(MetricCollectorImpl.java:283)
at
ru.andreymarkelov.atlas.plugins.promjiraexporter.servlet.AllEndpointFilter.doFilter(AllEndpointFilter.java:39)
2020-01-30 11:00:41,273 http-nio-8080-exec-321 ERROR anonymous
660x5246839x1 - 145.1.45.19 /plugins/servlet/prometheus/metrics
[r.a.a.p.promjiraexporter.service.MetricCollectorImpl] Error collect
prometheus metrics
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#61?email_source=notifications&email_token=AAPXM4FL3NABCNWM4XLV7BTRAKKKLA5CNFSM4KNRUXY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKKHIMQ#issuecomment-580154418>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPXM4F72C4IL6OSB3F7T63RAKKKLANCNFSM4KNRUXYQ>
.
--
*-- Andrey Markelov*
|
Hi Andrey |
Hi andrey Can you please check it? |
The same logs?
On Tue, Mar 10, 2020 at 00:39 agentchif ***@***.***> wrote:
Hi andrey
its still not working.
the same issue exist
i got only jvm_* metrics but not jira_* metrics
Can you please check it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#61?email_source=notifications&email_token=AAPXM4CE3J2PCJADGEZ7KCLRGXVCNA5CNFSM4KNRUXY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOKKZVY#issuecomment-596946135>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPXM4ENN2HF7XLTRJR6PA3RGXVCNANCNFSM4KNRUXYQ>
.
--
*-- Andrey Markelov*
|
hi andrey |
hi andrey |
hi |
hi andrey |
Hi |
i installed the add-on on Jira DC that contain 2 nodes and 1 Load balancer in front (haproxy).
i configure the prometheus config.yaml to scrape both nodes and put also labels on each node.
the scrape section at the prometheus config.yaml look like:
scheme: http
metrics_path: '/plugins/servlet/prometheus/metrics'
static_config:
labels:
nodeID: node01
ip: '145.1.45.141'
labels:
nodeID: node02
ip: '145.1.45.142'
the metrics that the exporter export to the prometheus are only jvm & process TYPES
there is no JIRA type at all
hence i cant measure metrics that related to jira like:
jira_issue_update_count
jira_user_login_count
jira_user_logout_count
etc....
anything that start with jira_
BTW,
i have the same configuration at bitbucket and there the bitbucket exporter is exporting bitbucket metrics include jvm & process
please assist here
The text was updated successfully, but these errors were encountered: