npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@itentialopensource/device-connection-health-check

v0.2.7-2023.1.0

Published

An Itential Automation Platform (IAP) device connection health check workflow.

Downloads

49

Readme

Device Connection Health Check

Table of Contents

Overview

This folder contains the Device Connection Health Check workflow, which is depicted in the following flowchart.

Legend

| Label | Description | | ------ | ------ | | A | Wait for a number of seconds (#ofSeconds) before attempting to connect/reconnect device. | | Connect | Attempt connection to the device and evaluate response. | | B | If connection is unsuccessful, try reconnecting a number of times (#ofTimes). | | C | If connection is successful, try connecting to the device for #ofSeconds.|

The workflow that is built connects to a device and attempts to connect for a certain #ofTimes to check stability. If the device is not alive, it will attempt to connect for a certain #ofTimes, after which it ends with a "fail" output. Output is "success" if the device connects successfully. Inputs are validated and produce a "bad input" error in case of wrong input.

This is how it relates to the flowchart:

This workflow is responsible for:

  1. Adding a delay for #ofSeconds before connecting to the device (before each retry).
  2. Attempting to connect to the device and getting a response (isAlive: true/false).
  3. If device is not alive, retry step 2 for #ofTimes.
  4. If device is alive, retry connecting consecutively with it #ofTimes (#retries).
  5. If step 4 fails during this duration, go back to step 3. The #retries for step 4 is reset here to 0 (reset consecutive counter).

Features

Features of this artifact include:

  • Auto-checks for input formatting errors.
  • Connects to the device and determines if the device is alive.
  • Waits for a certain amount of time before trying to establish a connection again.
  • Retries only for a certain number of times (numberOfRetries).
  • If connection to the device is successful, attempts for n - 1 more successful connections to the device (numberOfRetriesStability).

Requirements

The following job variables are required to start the workflow.

| Job Variable | Description | | ------ | ------ | | device | Name of device.| | pingDelay | Seconds to wait before trying to establish connection with the device again.| | numberOfRetries | Maximum number of times to attempt for a successful connection with the device.| | numberOfRetriesStability | The number requirement for consecutive successful connections (to validate interface stability).|

Supported Device Types

Devices residing on any adapter that implement device-broker (Ex. NSO, Ansible) are supported. One may use any device that shows up in Configuration Manager.

Test Environment

  • IAP version 2022.1

How to Run

Running the device connection health check is meant to be called from parent workflows during device upgrade or any other maintenance that require verification of connection stability. To test this workflow in stand-alone mode:

  1. Navigate to Workflow Builder.
  2. Click the play button next to the connection health check workflow.
  3. Supply the required inputs.
  4. Click start.

Additional Information

Please use your Itential Customer Success account if you need support when using this artifact.