/health endpoint show dmsg address & status of dmsg connection / current dmsg server

[0pcom]

we have the dmsg address as part of the /health endpoint or the service discovery, but not for the other skywire-services.

$  curl -sL http://conf.skywire.skycoin.com/ | jq | grep "http://" | cut -f 4 -d '"' | tac | while read _url ; do echo "$_url" ; curl -sL "$_url/health" | jq ; echo ; done

http://sd.skycoin.com
{
  "build_info": {
    "version": "f6eca01",
    "commit": "f6eca01551a269fcff71029c7c26c2b7c4862662",
    "date": "2023-06-23T10:48:51Z"
  },
  "started_at": "2023-06-26T12:55:14.333877441Z",
  "dmsg_address": "0204890f9def4f9a5448c2e824c6a4afc85fd1f877322320898fafdf407cc6fef7:80"
}

http://ut.skywire.skycoin.com
{
  "build_info": {
    "version": "4cde3fd",
    "commit": "4cde3fd6a455372b36adf4159f3f57b24ab788e7",
    "date": "2023-05-12T09:11:12Z"
  },
  "started_at": "2023-06-26T12:47:10.086609025Z"
}

http://rf.skywire.skycoin.com
{
  "build_info": {
    "version": "53ca588",
    "commit": "53ca588ee2aef919821a7bbfd2ace7a97ad62100",
    "date": "2023-06-09T13:27:31Z"
  },
  "started_at": "2023-06-24T12:46:52.644817158Z"
}

http://ar.skywire.skycoin.com
{
  "build_info": {
    "version": "0508925",
    "commit": "05089258e90e318f2080bbad5e5658abc9ddf0c9",
    "date": "2023-06-20T15:53:20Z"
  },
  "started_at": "2023-06-24T17:37:26.918692559Z",
  "dmsg_address": "03234b2ee4128d1f78c180d06911102906c80795dfe41bd6253f2619c8b6252a02:80"
}

http://tpd.skywire.skycoin.com
{
  "build_info": {
    "version": "53ca588",
    "commit": "53ca588ee2aef919821a7bbfd2ace7a97ad62100",
    "date": "2023-06-09T13:27:31Z"
  },
  "started_at": "2023-06-26T12:41:26.331154572Z"
}

http://dmsgd.skywire.skycoin.com
{
  "build_info": {
    "version": "v1.3.0-rc1-22-gcf0a8698",
    "commit": "cf0a86986740ad31a12fcc89a0ac0a0d77ed2ce0",
    "date": "2023-03-15T09:50:04Z"
  },
  "started_at": "2023-06-23T18:06:39.884084117Z"
}

Since the services can be accessed over either http or dmsghttp, perhaps it would be prudent to show

• The dmsg <pk>:<port> that the service is using

• The status of the dmsg connection

and / or

• The dmsg server which the service is connected to

[mrpalide]

About dmsghttp address of services, I check again, and everything is OK. The current missing on prod services related to old binaries. We will have update on them and use new binaries during next release of skywire.

But, dmsg-server address that services connected should implement.