Stream: troubleshooting

Topic: Dataverse Metrics API always returns 0 counts

Juan López (Apr 21 2026 at 14:57):

Hi everyone!

I'm currently experiencing an issue with the Metrics API in my Dataverse installation (6.10.1). All the endpoints are returning a count of "0", even though I already have content published in the system.

For example:

curl https://myDataverse.org/api/info/metrics/dataverses -> {"status":"OK","data":{"count":0}}
curl https://myDataverse.org/api/info/metrics/datasets -> {"status":"OK","data":{"count":0}}
curl https://myDataverse.org/api/info/metrics/files -> {"status":"OK","data":{"count":0}}

However, I currently have:
3 dataverses created
1 dataset published (with files)

Given this, I would expect the metrics to reflect those values.

Has anyone encountered a similar issue or knows what could be causing this behavior? Could it be related to indexing, metrics configuration, or background jobs not running?

Any guidance would be greatly appreciated.

Thanks in advance!

Philip Durbin 🚀 (Apr 28 2026 at 13:46):

@Juan López hi! Sorry for the slow reply. I was on vacation last week and I'm still catching up!

Philip Durbin 🚀 (Apr 28 2026 at 13:47):

I just went to /api/info/metrics/dataverses on what I think is your server and I see a count of 175. Is it working now? 201 datasets. 722 files.

Philip Durbin 🚀 (Apr 28 2026 at 13:49):

Oh, wait. Maybe I have the wrong server. It's running 6.8, not 6.10.1. :thinking:

Juan López (Apr 29 2026 at 16:47):

@Philip Durbin 🚀 Hi! thanks for your response. It is indeed a new instance, and as of today we’re starting to get values from the API calls. I’ll run a few tests to make sure everything is working properly.

Last updated: May 30 2026 at 09:11 UTC