A couple changes to SNO API

Node Operators
1

Hey everyone,

This is a heads-up that we’re making some changes to the SNO API soon.
From the endpoint for a single satellite:

  1. The uptime field is removed
  2. The online_score field is removed (see 3rd point)
  3. The audits field now uses the same structure as the audits field outputted by the satellites endpoint, which looks like this:
{
   auditScore
   suspensionScore
   onlineScore
   satelliteName
}

So, if you are using external tools which reference these fields, they may not work anymore.

Thanks!

10 Likes
2

Appreciate the announcement beforehand! Very thoughtful.

Apart from the move from online_score into audits the output itself does not change?

2 Likes
3

Actually, I’m glad you asked! It looks like the underlying structure of the audits field has changed, and I missed that. I’ll edit the description above.

1 Like
4

Does the new description answer your question?

5

Thanks for the heads up. Does this come with changes to the databases as well? Might need to adjust the earnings script accordingly. Perhaps you could point to the PR?

6

So for a single satellite this:

grafik
grafik613×728 22.3 KB

Will the onlineScore be added to the audit field os a single satellite too? (since there are both other audit scores)

Or only to the satellites endpoint?
grafik

Your working is a bit unclear to me in that point because there is only an “audits” field for satellites but the single satellite has “audit” field and a different structure. But the “audits” field of satellites already contains the onlineScore so probably not what you meant?

7

Sorry about that. Your picture of the single satellite with the crossed out sections is correct, except that the audit field is now identical to your second picture. Well, except that it won’t be an array, of course.

8

So in short the “audit” field will get an entry “onlineScore”/it moves into the audit field but no satelliteName obviously. That’s what I assumed, thanks.

9

We do plan to remove the uptime columns from the DB, yes.
This contains the API changes https://github.com/storj/storj/commit/6ba8f6c8a94eda74e7e4c170f874063a97b13391

2 Likes
10

So looking at that commit:

grafik
grafik730×355 8.28 KB

This actually means the “audit” field on the “satellite” endpoint is renamed into “audits” and actually includes the name of the satellite.

Now I understand it better, thanks.

11

@cameron Thanks a lot for announcing it in advance!

12

Given this, I’m guessing those of us that do depend on the API for extended tracking will need to update those scraper tools ( ie. Prometheus Storj-Exporter ).

What version is this change coming in?

13

I’m confused.

Frpom what I understand, 127.0.0.1:14002/api/sno/satellite/12t... will go from this:

  "audit": {
    "totalCount": 253,
    "successCount": 253,
    "alpha": 19.999955,
    "beta": 0,
    "unknownAlpha": 19.999955,
    "unknownBeta": 0,
    "score": 1,
    "unknownScore": 1
  },
  "uptime": {
    "totalCount": 567,
    "successCount": 567,
    "alpha": 0,
    "beta": 0,
    "unknownAlpha": 0,
    "unknownBeta": 0,
    "score": 0,
    "unknownScore": 0
  },
  "onlineScore": 1,

to this:

"audits": {
    "AuditScore": 1,
    "SuspensionScore": 1,
    "UptimeScore": 1,
    "SatelliteName": "12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo"
  },

With audit counts and alpha/beta values no longer being accessible.

Is this correct?

What’s “AuditHistory” ?

14

You will find the auditHistory under api/sno/satellite/. It will print out something like {“windowStart”:“2020-12-17T12:00:00Z”,“totalCount”:19,“onlineCount”:18} for the last 30 days with an interval of 12 hours.

1 Like
15

Thanks for the headsup

  1. If I’m reading this correctly we’re going to loose audit total count and replaced with history that’s only last 30 days? This will make it harder to estimate vetting which takes more then 30 days usually.
  2. Looking at https://github.com/storj/storj/commit/6ba8f6c8a94eda74e7e4c170f874063a97b13391 does this also rename sno/estimated-payout api endpoint to sno/estimated-payouts?
2 Likes
16

What version is this coming please? Wasn’t in 1.20.2.

17

@cameron an answer to the last 2 posts would be appreciated. thx

18

yes, all payout will be payouts now. In one of nearest, updates were finished, they are being tested and will be added in upcoming releases.

19

To the first point, that is correct. I agree that successful/total number of audits is useful information. @Nikolai_Seidov what do you think about putting those fields back?

To the second point, the name of the endpoint has not changed from what I can see. storj/server.go at c44368c489c3aac740df42f5a8af62a5aa115baf · storj/storj · GitHub

The changes are in v1.21.1 which is planned to be deployed today. I apologize for not responding sooner, felt a bit unwell last week :frowning:

8 Likes
20

No problem, thanks for the answer and get well!