Looking for how to get the transaction Log Details in the onapp Database? We can help you with this!

Here at Bobcares, we often handle requests from our customers to fix similar OnApp issues.

Today, let see how our Support Engineers fix this as a part of our Server Virtualization Technologies and Services.
 

Transaction Log Details in the onapp Database

 
We noticed so many cases of our customers that UI logs have been cleaned to make the UI look less messy. This is also helpful for hiding the transactions from the end-user view. After that, this won’t show the logs. But still, it is possible to view the log through the database.

We can use Virtual Machine identifier to see the transactions table with the following command to choose the log output we want to view:

mysql> select id, action, status, created_at, identifier from transactions where identifier='tbhgfglxilpehn';
+-----+----------------------------+----------+---------------------+----------------+
| id | action | status | created_at | identifier |
+-----+----------------------------+----------+---------------------+----------------+
| 197 | configure_operating_system | complete | 2015-02-23 18:01:38 | tbhgfglxilpehn |
| 198 | startup_virtual_machine | complete | 2015-02-23 18:01:38 | tbhgfglxilpehn |
| 199 | run_recipe_on_vm | failed | 2015-02-23 18:01:38 | tbhgfglxilpehn |
+-----+----------------------------+----------+---------------------+----------------+
3 rows in set (0.00 sec)

Now, we can select a specific transaction to view the output as follows:

mysql> select log_output from transactions where id=199\G
*************************** 1. row ***************************
log_output: [2015-02-23 18:06:00 UTC] Waiting for VS to boot...
[2015-02-23 18:06:00 UTC] VS is booted.
[2015-02-23 18:06:00 UTC] Waiting for VM to respond on port 22...
Fatal: VM network is down for 3600
Executing Rollback...
1 row in set (0.00 sec)

We can also use the same command if we have a disk identifier and want to see the disk-related task:

mysql> select id, action, status, created_at, identifier from transactions where identifier='g14vm6e7wcg07k';
+-----+--------------+----------+---------------------+----------------+
| id | action | status | created_at | identifier |
+-----+--------------+----------+---------------------+----------------+
| 194 | build_disk | complete | 2015-02-23 18:01:38 | g14vm6e7wcg07k |
| 196 | provisioning | complete | 2015-02-23 18:01:38 | g14vm6e7wcg07k |
+-----+--------------+----------+---------------------+----------------+
2 rows in set (0.00 sec)

After that, we can select a specific transaction to view the output.

We can also use other ways to filter the output only for completed or failed transactions:

mysql> select id, action, status, created_at, identifier from transactions where status='failed';
+-----+-------------------------+--------+---------------------+----------------+
| id | action | status | created_at | identifier |
+-----+-------------------------+--------+---------------------+----------------+
| 2 | create_hypervisor | failed | 2014-08-08 19:45:36 | hwy5hqseskdap3 |
| 54 | destroy_virtual_machine | failed | 2014-08-12 18:24:29 | ju1lulver2ta9r |
...
| 233 | take_incremental_backup | failed | 2015-04-06 15:06:28 | qug61mtcvhwlzm |
| 234 | take_incremental_backup | failed | 2015-04-07 15:06:26 | iyi6rra39f56jh |
+-----+-------------------------+--------+---------------------+----------------+
49 rows in set (0.00 sec)

[Need more assistance with OnApp queries? We’d be happy to do it for you]
 

Conclusion

 
In short, today we saw how our Support Techs help our customers to get the transaction Log Details in the onapp Database.