import_runtime
imports data from the opsview.runtime
database to the opsview.odw
database for long-term storage. If your Opsview does not use the Opsview Data Warehouse (ODW), you do not need to run import_runtime
.
By default, import_runtime
runs once every hour at 4 minutes past the hour: this is scheduled in the opsview
user’s crontab. You may want to run import_runtime
manually to troubleshoot issues with import_runtime
or to start the import process sooner than it would otherwise be scheduled.
Prerequisites
- Opsview is configured to use the ODW
Process
- Log in to the orchestrator as
root
. - Make sure
import_runtime
is not already running by checking to see if there is an existingimport_runtime
process:
ps -ef | grep import_runtime
If there is an existing import_runtime
process, it is safe to kill the process with kill
.
- Remove the
import_runtime
pid file if it exists:rm -f /opt/opsview/coreutils/var/import_runtime.pid
- Run
cleanup_import
to clean up any partially imported data from previous runs ofimport_runtime
:
/opt/opsview/coreutils/bin/cleanup_import
- Run
import_runtime
as theopsview
user:
sudo -iu opsview . /opt/opsview/coreutils/bin/profile && /opt/opsview/coreutils/bin/import_runtime -q &
Tracking import_runtime
progress
You can track the progress of import_runtime
with the Opsview - Data Warehouse Status
service check on the orchestrator. Alternatively, you can track import_runtime
progress on the command line using tail
and egrep
:
tail -f /var/log/opsview/opsview.log | egrep -i 'import\w* for'
Comments
0 comments
Please sign in to leave a comment.