This SAS KB article describes the initial data capture to collect for troubleshooting SAS Visual Investigator jobs running on SAS Viya 3.5. This article is helpful for any specific SAS Visual Investigator jobs, including the following:
- data indexing jobs
- entity resolution jobs
- alert generations jobs
- configuration import
Collecting troubleshooting data when you initially open a case expedites time to resolution by enabling SAS Technical Support to provide informed problem analysis.
Collect Data
I. Initial Questions
- What is the current version and hot fix level of your environment? (To locate this information, log on ► click your user icon in the top right corner ► select About.)
- In what type of environment does the issue occur? (That is, PROD, DEV, TEST, STAGE, and so on.)
- Do all jobs fail or just a specific job? If there is a specific job, provide additional details about the job.
- Has this job ever been successful in this environment? If yes, have you made any recent changes to the environment?
- Provide any additional details that can be shared regarding the business impact of this issue.
II. Data Collection
Share the following data collection with SAS Technical Support:
- Navigate to the Jobs page (Manage Investigate and Search ► Jobs) and capture a screenshot of the job for this scenario. Ensure that the screenshot captures the following:
- job name
- status
- start time
- end time
- run time
- error messages (if available)
- Logs from each of the OpenSearch/Elasticsearch environment: /opt/sas/viya/config/var/log/svi-elasticsearch
- Logs from each of the Microservices machines:
- /var/log/httpd
- /opt/sas/viya/config/var/log/svi-datahub
- /opt/sas/viya/config/var/log/svi-alert
- /opt/sas/viya/config/var/log/svi-visual-investigator
- /opt/sas/viya/config/var/log/svi-transport
- /opt/sas/viya/config/var/log/svi-feature
- /opt/sas/viya/config/var/log/svi-sand
- /opt/sas/viya/config/var/log/svi-indexer
- /opt/sas/viya/config/var/log/vsd-service
Related Information