- 26 Aug 2022
Using Itential Service Desk to Create a Support Ticket
- Updated on 26 Aug 2022
How to Access the Itential Service Desk
Support Ticket generation requires an Itential Service Desk (ISD) access account. To request access to the Itential Service Desk, contact your Itential Account representative.
Customers with a Service Desk account can access the Itential Service Desk and other related support tools using the Customer Portal link.
How to Create a Product Support Ticket
To generate a Product Support ticket:
Click the Login button in the upper-right corner of the screen.
Upon login, users will find a card display for the Service Desk and other related areas.
Click the Itential Service Desk card to access the Service Desk portal.
Select the appropriate category for the ticket that needs to be generated. Use the Ticket Category table below.Note:
Product support tickets generated outside of the Itential Service Desk against any other portals will be cancelled.
Select the appropriate ticket.
Click the appropriate item under the label “What can we help you with?”
Complete the ticket fields. Fields marked with red asterisks are required.
Click Send to submit the ticket.
|General Questions||Questions about the software, configuration, or other knowledge-seeking inquiries not otherwise covered on the https://docs.itential.com site.|
|Report a Problem||There is an active issue or a potential software bug that needs resolution.|
|Common Requests||This is a general category that covers topics like “New Features” Itential customers would like to see in future updates.
Note: New Feature Requests are reserved for Itential Core products only. If you have a request for any custom code or open-source components (including adapters and pre-builts), please open an issue directly in the repo location containing the code.
Impact Field Values and Definitions
The Impact field is displayed on the Service Desk portal page when the user selects "Report a software problem". To help you select the appropriate value for the Impact field, use the following definitions.
|Extensive / Widespread||Complete failure of the Application and no existing workaround is present; this may include executable crashes or situations where a major feature of the Application is inoperable.|
|Significant / Large||Complete failure of the Application and an existing workaround is present; failure of a non-critical feature.|
|Moderate / Limited||Failure of a minor feature or an Application usability problem.|
|Minor / Localized||Non-performance related issues, i.e. appearance of the Application.|
Share With Field
The Share with field at the bottom of the ticket is important and exists to ensure that SLAs for your organization are followed. Some members of a deployment may be contractors or other external delivery providers which provide services to more than one Itential customer. In these cases, the contractor generating the ticket will need to specify the organization to which the request relates (e.g. “Share with Acme Corp”).
Report a Production System Outage
Within the Report a Problem category, there is an option to report a Production System Outage. Please note, this option should only be used if your PRODUCTION system is actively experiencing an outage. General software problems in development or lab systems are not considered outages.
When reporting a Production System Outage, your conference bridge information is required and must be provided.
User related information (including tickets generated) can be found by clicking the Requests menu option next to your avatar in the upper-right corner of the screen.
To help you select the appropriate request type, use the following definitions.
|Created by me||This will display all tickets you have generated.|
|(Organization Name)||This will display a list of tickets generated for your associated organization.
Note: Depending on your company affiliations, you may have more than one organization name available to you.
|All||This will display a list of tickets for all organizations to which you belong.|
Ticket Status Options
When viewing a ticket list, the default status type will be "Open requests". You may change the status by clicking the associated drop-down menu and selecting a status from the list.
Status Updates and Comment History
Once a ticket has been created through the Service Desk portal, continue using the portal to view status updates and related conversation (comment history) threads. This is the primary method by which status updates are made available and communicated.
In the event that you receive an email update and you are away from your computer or logged out of the Service Desk Portal, you may respond to the email and your comments will be added to your ticket.
Does IAP have a log file for errors and other important information?
The Itential Automation Platform (Pronghorn) log files are typically stored in the
/var/log/pronghorn directory. If the log files are not found in that directory then check the
$PRONGHORN_BASE/properties.json file. Look at the value of the
loggerProps.log_directory to locate the log files.
Log messages can also be found in the
systemd journal using the following command.
sudo journalctl -f
See the manual (man) pages of
journalctl for more details.
How do I generate the "showsupport" output for my environment?
showsupport command-line utility is executed as the pronghorn process user. Use the following steps to generate the output:
SSH to your Itential host and login as the pronghorn process user.
Execute the following commands.
cd /opt/pronghorn/current ./showsupport ls -l ./showsupport*.gz
Download and attach the
showsupportfile to your Service Desk Ticket.
How do I generate a blueprint for my environment?
The blueprint is a generated JSON document of what is installed on the system, including out-of-box apps, adapters, as well as any custom apps and adapters, along with installed versions.
From the IAP home page:
Click Admin Essentials in the left navbar to open the application.
Click Blueprints in the Quick Start card and a dropdown menu displays.
Select Download to auto-generate and download the blueprint to your local machine to attach to your support ticket.
Alternately, use the Copy option to paste the contents in the Blueprint Output field on your support ticket.
Always include the contents of the Blueprint when you open ISD support tickets.