SIsraelyan's Posts

Thank you! One more question : have you considered upgrading to 4.5? You mentioned that your LI is 4.3, right ?
Hi, LI has a new feature called Dormant Hosts which is currently being tested and will become available in 4.6GA release. This feature monitors agents and hosts that send data to LI and alert... See more...
Hi, LI has a new feature called Dormant Hosts which is currently being tested and will become available in 4.6GA release. This feature monitors agents and hosts that send data to LI and alerts when it detects an agent(s)/host(s) NOT sending data to LI for some reason for the given/specified period of time.
Are you seeing the same behavior?
Bucket archiving (if archiving is enabled) or bucket retirement could be the reason why you are seeing different results.
I'll get back to you early next week with the details! Sincerely, Sam!
Hi, Log Insight has a new "Dormant Hosts" feature which triggers an alert when events stop coming in from a given host for a specified amont of time. Which LI version are you using ?
Hi, I am reposting this question internally to reach a broader audience to get this answered
You are welcome!
Hello, If you are sure there are no references to your LI, you can safely power off and delete it. If you have references, i.e. sources that send data to LI, then you should re-configure them... See more...
Hello, If you are sure there are no references to your LI, you can safely power off and delete it. If you have references, i.e. sources that send data to LI, then you should re-configure them. Sources: --- vSphere integration --- ESX integration --- Log Insight agents sending data to your LI However, since your LI is actually down, then  would recommend simply deleting the existing one and re-deploying LI. If your new LI gets the same network config, then you won;t need to do any reconfiguration. Hope this answered your question
Hello! There are two ways that you can delete a VM from vCenter: 1. you power off the VM and then "Remove from Inventory" -> this will *** NOT remove the VM files from disk 2. you power off ... See more...
Hello! There are two ways that you can delete a VM from vCenter: 1. you power off the VM and then "Remove from Inventory" -> this will *** NOT remove the VM files from disk 2. you power off the VM and then "Delete from Disk" -> this WILL remove all VM files I have attached a screenshot for you
Hello, If you reset your master node, you will lose the repository. If that;s OK with you, you could simply delete that node (the VM) and re-deploy it. Will that work for you?
There is a way to reset that node as it it were just deployed - would you like to reset that node ? Note that if you reset the node, you will lose any data that's been ingested before
The lock is created when the service is running, and there is no lock if the service is down. It is not the lock that's causeing the LI to fail booting.
Well, the service is not running, which means that you cannot access the ui. Try manually starting the service by executing: `service loginsight start` Run the command, wait for ~1-2 minz, and ... See more...
Well, the service is not running, which means that you cannot access the ui. Try manually starting the service by executing: `service loginsight start` Run the command, wait for ~1-2 minz, and then check the status of the service by running `service loginsight status` Thanks!
I am afraid that those nodes were deleted in such a way that it broke the cluster and now the service is not able to start normally. The nodes should be deleted from the admin/cluster page first... See more...
I am afraid that those nodes were deleted in such a way that it broke the cluster and now the service is not able to start normally. The nodes should be deleted from the admin/cluster page first, and then when they are removed from the cluster, you can then delete the VM files. Most likely it's Cassandra that cannot start. I assume that you have SSH access to the master node, so do the following: - ssh to the master node - run `service loginsight status` and see if the service is running - grep for errors in your runtime.log and see what u get Share the results once you have them! Thanks!
Hello! Please see my questions below: 1. What is the version of LI that you deployed? 2. When u say "three loginsight server", do u mean a cluster of 3 nodes ? 3. You said that you deleted ... See more...
Hello! Please see my questions below: 1. What is the version of LI that you deployed? 2. When u say "three loginsight server", do u mean a cluster of 3 nodes ? 3. You said that you deleted 2 worker nodes. Did u delete those from the admin/cluster page? 4. You cannot login to LI. What's the error message? Thanks!
That appears to be the case. I believe that those limits will be addressed soon as new feature requests/enhancements!
Actually not the table's limitation but a limitation on how many entries LI can export as csv
I believe that LI has a limit of 2K for the table. Can you decrease the timespan from 7 days to say 1 day and check the results ?
Yes, and this one - make sure you select "Table" as the chart type to see the data in tabular form