User Tools
This is an old revision of the document!
Table of Contents
Key Stats
Updated by Yanjun Wang 14/12/2021
Overview
The key_status is written with BASH&Groovy to provide customers with key information from their SnmpManager&Ticketer database.
The scripts need to be installed on each server/environment and run by a cronjob to refresh/update the data every day.
Due to each customer having a different DAS alarm workflow, form name etc. We have template all the scripts, and the script used to deploy can be generated based on configuration.
Generator Repo: https://bitbucket.org/errigal/key-stats/src/dev/
Scripts Generation and Installation
The scripts for each customer(Currently, support for ATC and EXT) can be generated by running the etl-tester locally, details as below:
- Imported the project in IntelliJ via Gradle and SpringBoot.
- Change clientCode in application.properties to either EXT or ATC.
- Run SpringBoot application, the customer based on key_stats script will be generated at {baseDir} which can be migrated to a server. (For both EXT and ATC, need to run twice)
More details for the generator at:here
Installation Playbook:
ansible-playbook -i ../env-configuration/os1/hosts.ini upload-key_stats-script.yml --ask-vault-pass
Table Details
Source: Reporting Manager KPI and BI Tool Integration IDMS 3.3 2017/2018
ticket_summary
Every ticket created in the Ticketer will correspond to exactly one row in this table. This table contains counts of all the major forms linked to a ticket. It also contains basic details of alarms triggered by SNMP trap.
ticket_summary
Every ticket created in the Ticketer will correspond to exactly one row in this table. This table contains counts of all the major forms linked to a ticket. It also contains basic details of alarms triggered by SNMP trap.
Appendix
Project folder:
