1.0.0 • Published 2 years ago

particle-status v1.0.0

Weekly downloads
1
License
MIT
Repository
github
Last release
2 years ago

particle-status

Node module to monitor the status of the components in the Particle Cloud status page.

Installation

npm install particle-status

Usage

Import the module:

const particle = require('particle-status')

Define an array with the names (or the indexes) of the components to be monitored (see Components):

// monitor Cellular Connectivity, REST API, Integrations

// use names of the components
components = [particle.CELLULAR_CONNECTIVITY, particle.REST_API, particle.INTEGRATIONS]

// use indexes of the components
components = [0, 2, 3]

It is also possible to monitor all the components:

components = particle.ALL_COMPONENTS

Check the status of monitored components:

particle.status(components, (err, status) => {
  if (err) {
    return
  }

  // do something with status object
  console.log(`operational: ${status.operational}`)
  console.log(`outages count: ${status.outage.length}`)
})

Components

These are the components available in the Particle status page

IndexComponentDescription
0CELLULAR_CONNECTIVITYGeneral reachability of devices such as Boron and Electron to and from the Particle Cloud over cellular networks
1WIFI_CONNECIVITYGeneral reachability of devices such as Argon & Photon to and from the Particle Cloud over WiFi networks
2REST_APIapi.particle.io endpoints not related to device reachability and SIM management, impacts to these endpoints are captured via Cellular Connectivity, Wifi Connectivity, and Telephony Providers components
3INTEGRATIONSSystems responsible for delivering events generated via Particle.publish to external systems such as Azure IoT, Google IoT, or custom http endpoints (webhooks)
4MANAGEMENT_CONSOLECovers availability of Particle's primary device management interface at https://console.particle.io
5TELEPHONY_PROVIDERSConnectivity of cellular devices and SIM state management
6CUSTOMER_RESOURCESStore, documentation, community forum, web-based IDE (build.particle.io), main website
7DEVELOPER_TOOLSParticle Workbench and Particle CLI

Status format

The status object contains two fields:

  • operational: determine if every monitored component is operational
  • components: contains three arrays (operational, outage and minor) with the components that are operational or affected by major or minor outages

Example with all systems operational

{
	"operational": true,
	"components": {
		"operational": [
			{
				"status": "operational",
				"name": "api.particle.io"
			},
			{
				"status": "operational",
				"name": "Mobile carriers"
			},
			{
				"status": "operational",
				"name": "Webhooks"
			}
		],
		"outage": [],
		"minor": []
	}
}

Example with some monitored system affected by the outage

{
	"operational": false,
	"components": {
		"operational": [
			{
				"status": "operational",
				"name": "Mobile carriers"
			}
		],
		"outage": [
			{
				"status": "outage",
				"name": "api.particle.io"
			},
			{
				"status": "outage",
				"name": "Webhooks"
			}
		],
		"minor": []
	}
}
1.0.0

2 years ago

0.2.0

5 years ago

0.1.3

5 years ago

0.1.2

5 years ago

0.1.1

5 years ago

0.1.0

6 years ago