# SNO API new fields? ("atRestTotalBytes", "intervalInHours")

**URL:** <https://forum.storj.io/t/sno-api-new-fields-atresttotalbytes-intervalinhours/21014>\
**Category:** troubleshooting\
**Tags:** monitoring, storagenode-api, prometheus\
**Created:** [January 14, 2023, 12:56pm UTC](https://forum.storj.io/t/sno-api-new-fields-atresttotalbytes-intervalinhours/21014 "2023-01-14T12:56:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![striker43](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/striker43/32/1135_2.png) [@striker43](https://forum.storj.io/u/striker43)\
**Post date:** [January 14, 2023, 12:56pm UTC](https://forum.storj.io/t/sno-api-new-fields-atresttotalbytes-intervalinhours/21014/1 "2023-01-14T12:56:03Z")

</div>

Hi,  
I just discovered that for one of my nodes the prometheus exporter is failing and also my self-scripted monitoring-tool is not able to parse the storagenode api json anymore.  
There seem to be new fields under /api/sno/satellites/storageDaily which are “atRestTotalBytes” and “intervalInHours”. The weird thing is that the one node where I see these new fields is updated to version 1.70.2, but I have 5 other nodes that are already on 1.70.2 and they don’t have these new fields in their api endpoints.

How is that possible?

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [January 15, 2023, 3:12am UTC](https://forum.storj.io/t/sno-api-new-fields-atresttotalbytes-intervalinhours/21014/2 "2023-01-15T03:12:38Z")

</div>

Perhaps these fields are empty on those other nodes and thus not reported. But I believe that they would have a values sooner or later.  
Maybe databases on your other 5 nodes are corrupted, you may check them:

> **[How to fix a "database disk image is malformed"](https://support.storj.io/hc/en-us/articles/360029309111-How-to-fix-a-database-disk-image-is-malformed-)**
>
> Problem
> Sometimes a Storage Node Operator may encounter the "database disk image is malformed" error in their log. This could happen during unplanned shutdown or reboot. The error indicates that on...