This web-server supports following services:
- JqlTableauExtractService - extracts data from JIRA into Tableau as native TDE file.
- sampleWorkflow - records sampleWorkflow-transitions in DB (used by RQC reports, etc)
- sampleAnalyticsWorkflow - new version sampleWorkflow
- labopsjira / BspFreezerLocations - support SRS tools
- CromwellViewer - monitor pipeline workflows (see also Cromwell API)
- txtExtract - extract data from datamarts as csv/tsv
- IlluminaSummary - used by John Walsh to upload summary-file to DWH
- IlluminaMetrics - used by Walsh to upload "barcodeCounts" files to DWH
- DependencyVisualizer
- ETLDashboard - ATTN: Actual ETLs (running on UNIX) are not affected even if Dashboard is down.
- http://analytics:8090/etl_runs?latest_run_only=true shows only latest run for each agent.
- "generate_sql" service generates automatically a JIRADWH query for extracting data from JIRA
- JiraWebConnector - alternative interface to get data into Tableau (failed to gain popularity)
codeAssistant
troubleshooting tools: sqlMonitor, peekattable, LockedObjects,
Services in red above are being used in production tools, others are for development and maintenance purposes.
CromwellViewer
txtExtract service
created in December 2018 (see RPT-5119, RPT-5179)
Obtain data as a direct extract from Analytics REST API by running this curl command from any UNIX server, Windows command prompt, or Mac terminal.
command: curl -XGET -F file="@<YOUR_SOURCE_FILE>" "http://analytics:8090/api/v2/csvExtract?extractName=<YOUR_EXTRACT_NAME>" -o <RESULTS_FILE>
Extending the service:
A number of configuration files live here: \\neon-cifs\home_unix\analytics\TigerETL3\resources
extractSQL.conf is one of the files, called by the csvExtract service. Within this file is the ETL transformation it uses. Adding new SQL parameters within it allows us to extend to new curl commands.
To extend the service, another section (parameter) must be added to the extractSQL.conf file, specifying the input file parsing and the SQL to produce desired output.
After the conf file is edited, the analytics webserver must be forced to refresh it (otherwise, the webserver will use the version of the file as it was upon webserver restart). You can force an "extractSQL.conf" reload with this http://analytics:8090/api/v2/csvExtract
Troubleshooting
If any of these services gets in trouble, the easiest way to bring it back might be to restart the Web Server (analytics server - useful tools and commands)