Name: Remedy-Application-Statistics
Owner: Los Alamos National Laboratory
Description: Remedy Application Statistics are a series of forms and workflow designed to help Remedy Administrators collect usage and performance data about their Remedy applications. This workflow is part of a presentation that was given at the T3 Conference (Tools, Technology, Training) hosted in Las Vegas between November 6, 2017 to November 10, 2017.
Created: 2018-05-09 15:36:59.0
Updated: 2018-05-09 17:31:49.0
Pushed: 2018-05-09 17:29:16.0
Size: 3616
Language: null
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Thank you for your interest….
Import the DEF file into your Remedy Development environment
Open BMC Remedy Developer Studio application
Select File drop-down menu and choose Import
Follow the steps in the wizard to import all forms and workflow from the DEF file
Import the XML file into your BMC Smart Reporting Development environment
Login to BMC Smart Reporting using account with admin rights
Select Administration drop-down menu and choose Import
Upload the XML file and follow the steps in the wizard to import the custom Views, Reports, and Dashboards
Once the import of forms and workflow has been completed, you will need to adjust some workflow based on your environment. This workflow was built using a three Remedy application server environment. If you have more than three servers, some extra work might need to be involved to capture their statistical data as well.
Update LANL:ADM:Combined Application Statistics form
Open form LANL:ADM:Combined Application Statistics form in BMC Remedy Developer Studio
Rename field “Check Server 1” to actual server name of your first application server
(if 2nd server present) Rename field “Check Server 2” to actual server name of your first application server
(if 3nd server present) Rename field “Check Server 3” to actual server name of your first application server
Update LANL:ADM:Combined Server Statistics form
Open form LANL:ADM:Combined Server Statistics form in BMC Remedy Developer Studio
Rename field “Check Server 1” to actual server name of your first application server
(if 2nd server present) Rename field “Check Server 2” to actual server name of your first application server
(if 3nd server present) Rename field “Check Server 3” to actual server name of your first application server
Update Filter Workflow
Update the follow Filters to ensure their Qualification statements properly reflect the changed field values from the previous steps.
LANL:ADM:Set Server Statistics Server 1
LANL:ADM:Set Server Statistics Server 2
LANL:ADM:Set Server Statistics Server 3
LANL:ADM:Set Application Statistics Server 1
LANL:ADM:Set Application Statistics Server 2
LANL:ADM:Set Application Statistics Server 3
Update LANL:ADM:Set Statistic Status Completed
Update Filter LANL:ADM:Set Statistic Status Completed to reflect proper number actual servers in your environment.
(1 Server) ($Check Server 1$ != $NULL$)
(2 Server) ($Check Server 1$ != $NULL$) AND ($Check Server 2$ != $NULL$)
(3 Server) ($Check Server 1$ != $NULL$) AND ($Check Server 2$ != $NULL$) AND ($Check Server 3$ != $NULL$)
Update LANL:ADM:Set App Stat Status Completed
Update Filter LANL:ADM:Set App Stat Status Completed to reflect proper number actual servers in your environment.
Enable Server Statistics
Make sure that Server Statistics is enabled on your AR System Administration Console.
Workflow built around a setting of 300 seconds (5 minutes) Cumulative Queue collection.
Enable Application Statistics
Login to your Remedy website using an account with admin rights.
Open form Application Statistics Configuration (may need to use Mid-Tier Object List).
Create entry for each Deployable Application to capture statistics on. For example: Logging Status: Enabled Logging Type: Application Name: Remedy Incident Management Logging Interval (sec): 300
You should now be good to start collecting various statistics about your Remedy application's usage by users. Feedback and suggestions are always welcome.
If you are using more than three (3) Remedy application servers, then you will need to adjust more workflow to capture data from any other servers beyond the initial three. I prefer to use separate fields to capture data of each server on the forms LANL:ADM:Combined Application Statistics and LANL:ADM:Combined Server Statistics. However, you could potentially reuse existing fields even though this would make it harder to discern individual collected stats from each server when troubleshooting errors or conflicts.
Form Updates LANL:ADM:Combined Server Statistics
Open the form LANL:ADM:Combined Server Statistics in BMC Remedy Developer Studio
Add new checkbox field “Check Server 4” or using actual server name
Add new Tab for each additional server in group to be collected
Copy fields from tab Server 1 into the new tab
Rename new fields accordingly (i.e. API Calls Count1 to API Calls Count4)
Repeat previous steps on form LANL:ADM:Combined Application Statistics
Create Filter LANL:ADM:Set Server Statistics Server 4
Copy filter LANL:ADM:Set Server Statistics Server 1 to LANL:ADM:Set Server Statistics Server 4
Update Qualification to reflect the fourth server name in your server group
Update Push If Qualification to use new “Check Server 4” field
Update Push To Fields to direct data to newly created fields (i.e. $Create Entry Calls Count4$ = $Create Entry Calls Count$)
Repeat previous step for LANL:ADM:Set Application Statistics Server 4
Update LANL:ADM:Set Statistic Status Completed
Update Qualification to reflect newly created “Check Server 4” field on form LANL:ADM:Combined Server Statistics
Update LANL:ADM:Set App Stat Status Completed
Update Qualification to reflect newly created “Check Server 4” field on form LANL:ADM:Combined Application Statistics
Repeat for each additional Remedy Application Server.
Remedy Application Statistics is released under the BSD 3-Clause License. For more details see the LICENSE.txt file.
LANL code designation: C18046