---
title: "Querying Server Statuses Using the API"
canonical: "https://docs.infoblox.com/space/BloxOneInfrastructure/282853467/Querying%20Server%20Statuses%20Using%20the%20API"
format: markdown
---
The Infoblox platform provides the `statuses` API call, so you can query the following statuses on a specific NIOS-X server:

- Server status
- Platform service status
- Protocol service status


You can use the following curl command to query server statuses:

`curl -k "https://<Server IP address>/api/hostmonitoring/v1/statuses" --header 'Accept: application/json' | jq`

Server Metric Connector returns a response based on the following schema:

`{`  
`    Object    string  // ntp, cdc, host, platform etc.`  
`    SubObject string  // health, network-connectivity, upgrade etc.`  
`    State     string  // started, stopped, online, degraded etc.`  
`    Severity  string  // info, warn, error etc.`

`    Messages  json`  
`    Metadata  json     // ophid, pool_id, service_id (if applicable), host, account_id, identity_account_id, host_id, host_uuid and other relevant labels`  
`    UpdatedAt time.Time  This is the timestamp when Infoblox Platform last polled the health-reporter and got an update about changes in the status.`  
`}`

The following is an example of a response:

`"object": "dns",`  
`"sub_object": "health",`  
`"state": "started",`  
`"severity": "info",`  
`"message": [],`  
`"metadata": {`  
`  "pool_id": "infra/pool/xxxxxxxxxx",`  
`  "ophid": "xxxxxxxxxx",`  
`  "account_id": "xxxxxx",`  
`  "host": "xxxxxx",`  
`  "host_id": "xxxxx",`  
`  "service_id": "infra/service/xxxxxxxxxxx"`  
`},`  
`"updated_at": "2024-04-04T18:29:18.5790770xxx"`

# Severity Levels for Status Events

The following table lists all possible severity levels for the status events:

| **Displayed Name** | **Severity Level** | **System Response** |
| --- | --- | --- |
| emerg | Emergency | <span style="color: #3e5656">System unusable</span> |
| alert | Alert | <span style="color: #3e5656">Immediate action needed</span> |
| crit | Critical | <span style="color: #3e5656">Critical conditions exist</span> |
| error | Error | <span style="color: #3e5656">Error conditions exist</span> |
| warn | Warning | <span style="color: #3e5656">Warning conditions exist</span> |
| notice | Notice | <span style="color: #3e5656">Normal but significant conditions exist</span> |
| info | Informational | <span style="color: #3e5656">Informational messages</span> |
| debug | Debug | <span style="color: #3e5656">Debug messages</span> |

<span style="color: #000000">In addition, you can query a server's metrics, by using the following curl command:</span>

`    curl -k "https://<server IP address>/api/hostmonitoring/v1/metrics" --header 'Accept: application/json' | jq`

Server Metric Connector returns a response based on the following schema:

`{ `

`    Name string // The name of the metric.`  
`    ``Help string // Help text for the metric.`  
`    ``Type string // Type of the metric (e.g., GAUGE, COUNTER, HISTOGRAM etc).`  
`    ``Metrics json // ophid, pool_id, host, account_id, identity_account_id, host_id, host_uuid and other relevant labels along with the value of the metric.`  
`}`

<span style="color: #000000">The following is an example of a response:</span>

`"name": "xxxxxx"`  
`"help": Combined CPU percentage used on the host for all cores",`  
`"type:: "GAUGE",`  
`"metrics": [`  
`{`  
`    "labels": {`  
`      "account_id": "xxxxxx",`  
`      "host": "xxxxxx",`  
`      "host_id": "xxxxxx",`  
`      "ophid": "xxxxxxxxxxx",`  
`      "pool_id": "infra/pool/xxxxxxxxxx"`  
`     },`  
`     "value": "x.xx"`  
`   }`  
`  ]`  
`},`