Last updated at Fri, 03 Nov 2017 13:29:25 GMT

Last week we discussed new ways a User can install our Windows Agent from the command line.

Now we’ll explore even more goodies for Users who use the command line on Windows.

Over the past month we have been updating our Windows Agent to make it more powerful for our growing customers needs. One particular area we felt needed updating was the Command Line capabilities of the Windows Agent.

You can now become a Windows Agent Power User from the command line without ever needing to look at a GUI!

Windows Agent Power User

Following files

If you are an active Logentries User (or even just a first-time user) then Following Files is something that you will be doing continuously when setting up or updating your Windows Agent configuration. Now you can perform a simple follow command from the Command Line to speed up the process of follow large number of log files in your System.

Simply run

AgentService follow PATH_TO_FILE

The Agent will notify you it is now following that particular file, and it will restart the service so that the change is made live.

Removing inactive logs

Unfortunately, not all logs live forever and in this situation it can be frustrating to see inactivie logs clutter your setup. Removing these old logs is extremely straight forward.

AgentService remove PATH_TO_FILE

Now the Agent will no longer follow that file that is cluttering your configuration.

What am I following anyway?

As an active user of Logentries I am always forgetting what my Agent is actually following. Many times I have been logged into a machine and thought “what is this machine sending to Logentries again?”

Thankfully the solution is now here!

AgentService list

Now you can refresh your mind about which logs are being sent to Logentries, which will include the File Path, and the Logentries Token that the log is using!

What’s my version again?

In a world of seamless updates it is always helpful to keep track of what version your software is running. We make this even easier now by not only printing your current version that you are running, but printing the version number of the latest Agent that is available!

How will I remember all of these awesome commands?

A helping hand is always one with the Windows Agent; if you run a command that is not detected we will print out the list of valid commands.

Furthermore if you find yourself stuck you can always run AgentService help to print all available commands of the Windows Agent.