• 1
  • 2
  • 3

0.20 | Updated: 23 Mar 2018



Downloads of v 0.20:



Software Author(s):

  • Papertrail Inc.

  • 1
  • 2
  • 3
remote_syslog2 0.20

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.


Deployment Method: Individual Install, Upgrade, & Uninstall

To install remote_syslog2, run the following command from the command line or from PowerShell:


To upgrade remote_syslog2, run the following command from the command line or from PowerShell:


To uninstall remote_syslog2, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade remote-syslog2 -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade remote-syslog2 -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install remote-syslog2
    name: remote-syslog2
    version: '0.20'
    state: present

See docs at

chocolatey_package 'remote-syslog2' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.20'

See docs at

cChocoPackageInstaller remote-syslog2
    Name     = "remote-syslog2"
    Version  = "0.20"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'remote-syslog2':
  ensure   => '0.20',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator gep13 on 26 Mar 2018.


remote_syslog tails one or more log files and sends syslog messages to a
remote central syslog server. It generates packets itself, ignoring the system
syslog daemon, so its configuration doesn't affect system-wide logging.


  • Collecting logs from servers & daemons which don't natively support syslog
  • When reconfiguring the system logger is less convenient than a
    purpose-built daemon (e.g., automated app deployments)
  • Aggregating files not generated by daemons (e.g., package manager logs)

This code is tested with the hosted log management service Papertrail
and should work for transmitting to any syslog server.

remote_syslog2 is a rewrite of the ruby [remote_syslog] package. Not all
features of the ruby version are supported, and there are some backwards
incompatible changes.

$packageArgs = @{
  packageName            = "$env:chocolateyPackageName"
  url                    = ''
  url64bit               = ''
  UnzipLocation          = "$env:TMP"
  checksum               = 'd5f907200d7a49131ceea04d2d70bf903fde6985fd1c60106d98ab5cef5146c6'
  checksum64             = '933bedeb12d09be373924a40975232eb3c15030f4cea3599278f35289e4872e2'
  checksumType           = 'sha256'
  checksumType64         = 'sha256'
Install-ChocolateyZipPackage @packageArgs

$packageArgs = @{
  FileFullPath           = "$env:TMP\remote_syslog_windows_i386.tar"
  FileFullPath64         = "$env:TMP\remote_syslog_windows_amd64.tar"
  Destination            = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
Get-ChocolateyUnzip @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
remote_syslog2 0.19 138 Friday, August 10, 2018 Approved
remote_syslog2 0.18 130 Friday, August 10, 2018 Approved
remote_syslog2 0.17 138 Friday, August 10, 2018 Approved
remote_syslog2 0.16 137 Friday, August 10, 2018 Approved
remote_syslog2 0.15 137 Friday, August 10, 2018 Approved

This package has no dependencies.

Discussion for the remote_syslog2 Package

Ground Rules:

  • This discussion is only about remote_syslog2 and the remote_syslog2 package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or remote_syslog2, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus