search

peimanja / artifactory_exporter

JFrog Artifactory Prometheus Exporter written in Go
Apache License 2.0
141 stars 37 forks source link

No metric named 'artifactory_artifacts_created_1m' and so on.. #89

Closed king4sun closed 1 year ago

king4sun commented 1 year ago

Hello there, when I ran this exporter and push data to Prometheus and show dashboard in Grafana, I came into a problem: artifactory_artifacts_created_1m, artifactory_artifacts_downloaded_1m and so on are missing.

The dashboard file is also created by peimanja from here

The exporter version is v1.9.5.

Do you know why the metric is lost and the solution?

king4sun commented 1 year ago

level=error ts=2022-12-09T02:12:49.287Z caller=artifacts.go:77 msg="There was an error finding artifacts" queryType=created period=1minutes error="Post \"http://127.0.0.1:8081/artifactory/api/search/aql\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"

peimanja commented 1 year ago

Hey @king4sun, do you have many artifacts getting pushed or downloaded from Artifactory? Looks like the query is timing out. the default timeout is 5s but try increasing it and see if that resolve your issue.

if you are using the helm chart:

options:
  timeout: 10s

you can set time out using --artifactory.timeout=10s flag or set the ARTI_TIMEOUT environment variable

king4sun commented 1 year ago

thanks for your reply @peimanja .

  1. Yes and there soooo many artifacts transfered per minute.
  2. I have tried timeout 10s ,there is no timeout error but still no metric.
  3. In addtion I test AQL with PostMan to do a post request, it's ok.

No more ideas for this now...

peimanja commented 1 year ago

thanks for your reply @peimanja .

  1. Yes and there soooo many artifacts transfered per minute.

  2. I have tried timeout 10s ,there is no timeout error but still no metric.

  3. In addtion I test AQL with PostMan to do a post request, it's ok.

No more ideas for this now...

Can you try enabling debug log and see if anything shows up there?

Maybe also try increasing the timeout a little more

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.