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

wbb-solarwinds

v0.0.7

Published

SolarWinds is a modern IT service management (ITSM) solution to eliminate barriers to employee support services. You can use this integration to raise Incidents directly from your digital assistant.

Downloads

5

Readme

SolarWinds

With this integration you can create Incidents in the SolarWinds Service Desk platform. Information about the Incidents you can create can be found here -> https://apidoc.samanage.com/#tag/Incident. Note that other types of ticket are not yet supported.

Blocks Provided

At present, only two blocks are provided for SolarWinds, and it is explained below.

|Handler Name|Purpose| |------------|-------| |Create Indicent|This block will ask any necessary questions, and once complete send the data to the APIs to create the Incident. Parameters, explained below, allow you to determine what happens next.| |Settings Error|Used whenever the blocks are used with an incorrect set of parameters.|

Handler Names

The following handler names and their functions are available :

|Handler Name|Purpose| |------------|-------| |create-incident|Raise a new Incident using the information provided and provide a ticket number back to the user.|

Configuration Options

Within the function there are a number of options that can be set to configure the behaviour of the integration. The tables below show the settings that are available for each handler.

create-incident

|Property|Required|Description| |--------|--------|-----------| |api_token|true|The API authentication token for use with API calls. Please see https://apidoc.samanage.com/#section/General-Concepts/Authentication for more information. | |root_url|true|The root URL for API calls, typically either https://apieu.samanage.com or https://api.samanage.com | |requester|true|Either a static email address of the requester, or the name of a property contained within the form submitted. For example, either [email protected] or email to pull the email address from a form question. | |assignee|true|Either the id of an assignee to be associated with this Incident, or an object. In the case where its an object this value will be passed through directly. | |category|true|This can either be a string, or an object. In the case where its a string, it'll set the category to the one whos name matches the value provided. If its an object it will be passed through directly. | |subcategory|true|This can either be a string, or an object. In the case where its a string, it'll set the subcategory to the one whos name matches the value provided. If its an object it will be passed through directly. | |priority|false|A string representing the priority for this incident, ie Low. | |state_id|true|The state_id to be used when creating this ticket. | |site_id|false|Passed directly through as the site_id parameter on the Incident.| |department_id|false|Passed directly through as the department_id parameter on the Incident.| |name|true|This can either be a static string, or the property name from within the form data submitted. In the latter case the name of the ticket will be set to what the user entered in the form. | |description|true|This can either be a static string, or the property name from within the form data submitted. In the latter case the desription of the ticket will be set to what the user entered in the form. | |response_string|true|A String containing a response to the user. This string can contain the following parameters, id, number, ticketName, ticketDescription, assignee, and link, along with anything provided in the settings of the block. Parameters must be enclosed in double %% and if set correctly will be substituted with the relevant properties from the new Incident created. For example, Ticket Number is %%number%% will return to the user Ticket Number is 12345.| |next_block|false|If set, will direct the user to this block ID to continue the conversation. | |error_block|true|The block ID to use for cases where the creation of the Incident has failed.| |live|false|If set to true will call the API and create the incident. If not set, or set to false then it'll return dummy information. |