Device health monitoring using Ping - SORACOM IoT Template Gallery

This guide explains the overview, setup, and usage of the Device health monitoring using Ping app.

Overview

Device health monitoring using Ping is a Flux app that automatically performs downlink connectivity checks (Ping) on SORACOM IoT SIMs and notifies the results to Slack. It is useful for monitoring IoT device connectivity and automating operations. It is based on the use of sendDownlinkPing.

Execute downlink Ping to a specified SIM ID
Obtain Ping results (success/failure, statistics, RTT, etc.)
Automatic notification to Slack
Customizable check interval, retry count, and timeout

You can change the check interval, retry count, and timeout in the settings.

Device health monitoring using Ping Result Example

:signal_strength: Downlink Ping Result

Success: true
Stat: 1 packets transmitted, 1 received, 0% packet loss, time 0ms
RTT: rtt min/avg/max/mdev = 47.834/47.834/47.834/0.000 ms

Estimated Costs

Initial Costs

Item	Cost	Notes
SORACOM IoT SIM	From 902 yen	SORACOM IoT SIM Estimate (plan-D D-300MB) Required if you do not already have a SORACOM IoT SIM.

Monthly Costs

Item	Estimated Cost	Notes
SORACOM Flux	491.04 yen/month (*1)	4,464 events/month when executed at 10-minute intervals (*2)
SORACOM IoT SIM	From 55 yen/month	Monthly fee for SORACOM IoT SIM or SORACOM Arc (*3). “From 55 yen/month” is the monthly fee for SORACOM Arc.

(*1) The SORACOM Flux Developer plan includes up to 10,000 events/month free per account. Events exceeding 10,000/month are charged at 0.11 yen per event.
(*2) When the application runs at 10-minute intervals, this Flux app will execute up to 4,320 events per month (31 days).
Event counts and credits are initially set to the same upper limits as the free bundle allocation. When the limit is reached, app launches and action executions triggered by events will no longer occur. If you wish to use beyond these limits, please update the limits in advance. When you set limits that exceed the monthly bundle allocation, excess events and credits will be available on a pay-as-you-go basis.
(*3) In addition to the monthly base fee, data communication charges apply. For details on data communication charges, please refer to Japan Coverage IoT SIM and SORACOM Arc.

This is an estimate and may vary based on actual usage. For accurate pricing, please check the Pricing & Fee Schedule and usage details in the User Console.

Prerequisites

Before deploying this template, please prepare the following:

Slack Webhook URL (obtain from your Slack channel)
IoT SIM with downlink communication enabled

Creating the App

At the time of app creation, you will need the Slack Incoming Webhook URL for notifications. Please refer to Using Incoming Webhooks to Trigger Flux Apps to create the URL.

Parameter Settings

Parameter Name	Description	Example
Slack Webhook URL	Webhook URL for Slack notifications	https://hooks.slack.com/services/…
SIM ID	IoT SIM ID to check	1234567890abcdef123
Downlink Check Interval	Interval between checks	10 minutes
Number of Ping Requests	Number of ping requests (1-5)	1
Timeout Seconds	Timeout in seconds (1-3)	1

Customizing the App

You can change the notification timing and content in the Slack notification action settings screen.

Click the [Slack Notification] action in Flux Studio.

To change the notification timing, modify the [Action Condition] such as ‘payload.success == false’ (notify only when monitoring fails).

To change the notification content, modify the [Payload] as needed.

You can use operators and functions in conditions. For details, see Use Expressions in Actions.

Troubleshooting

No notification received
- Check if the Slack Webhook URL is correct.
- Check if the SIM ID and parameters are correct.
- Check if the SIM is active and downlink communication is enabled on SORACOM.

If it does not work as expected, please check the app execution history. For details, see View Logs.