Downloads:

1,621,485

Downloads of v 2.10.2150:

595,036

Last Update:

09 Dec 2018

Package Maintainer(s):

Software Author(s):

  • james.crowley
  • petemounce
  • kurtglastetter
  • mykola.shestopal

Tags:

nxlog syslog admin

NXLog Community Edition

2.10.2150 | Updated: 09 Dec 2018

Downloads:

1,621,485

Downloads of v 2.10.2150:

595,036

Software Author(s):

  • james.crowley
  • petemounce
  • kurtglastetter
  • mykola.shestopal

NXLog Community Edition 2.10.2150

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install NXLog Community Edition, run the following command from the command line or from PowerShell:

>

To upgrade NXLog Community Edition, run the following command from the command line or from PowerShell:

>

To uninstall NXLog Community Edition, run the following command from the command line or from PowerShell:

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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 https://chocolatey.org/api/v2. 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. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade nxlog -y --source="'STEP 3 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 nxlog -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure nxlog installed
  win_chocolatey:
    name: nxlog
    state: present
    version: 2.10.2150
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'nxlog' do
  action    :install
  version  '2.10.2150'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: nxlog,
    Version: 2.10.2150,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller nxlog
{
   Name     = 'nxlog'
   Ensure   = 'Present'
   Version  = '2.10.2150'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'nxlog':
  provider => 'chocolatey',
  ensure   => '2.10.2150',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install nxlog version="2.10.2150" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 05 Nov 2019.

Description

nxlog is a modular, multi-threaded, high-performance log management solution with multi-platform support. In concept it is similar to syslog-ng or rsyslog but is not limited to unix/syslog only. It can collect logs from files in various formats, receive logs from the network remotely over UDP, TCP or TLS/SSL . It supports platform specific sources such as the Windows Eventlog, Linux kernel logs, Android logs, local syslog etc. Writing and reading logs to/from databases is also supported.


tools\chocolateyInstall.ps1
$packageName = 'nxlog-ce'
$installerType = 'msi'
$toolsDir   = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
$fileLocation = Join-Path $toolsDir 'nxlog-ce-2.10.2150.msi'
$silentArgs = '/qn'

Install-ChocolateyInstallPackage $packageName $installerType $silentArgs $fileLocation
tools\LICENSE.txt
From: https://nxlog.co/nxlog-public-license

NXLOG PUBLIC LICENSE v1.0

1. DEFINITIONS
“License” shall mean version 1.0 of the NXLOG PUBLIC LICENSE, i.e. the
terms and conditions set forth in this document;
“Software” shall mean the source code and object code form, all associated
media, printed materials, and "online" or electronic documentation. All
such software and materials are referred to herein as the "Software" and
are copyrighted by Licensor;
“Licensor” refers to the copyright holder of the Software, i.e. NXLog Ltd.

2. GRANT OF LICENSE
Licensor hereby grants you the following rights, provided that you comply
with all of the restrictions set forth in this License and provided,
further, that you distribute an unmodified copy of this License with the
Software:
i. You may copy and distribute verbatim (i.e. unmodified) copies of the
Software as you receive it, in any medium;
ii. You may modify the Software, create works based on the Software and
distribute copies of such, in any medium.

By downloading, using, modifying and copying the Software (or any work
based on the Software), you indicate your acceptance of this license to
do so, and all its terms and conditions for using, copying, distributing
and modifying the Software or works based on it. Nothing other than this
license grants you permission to modify, distribute the program or its
derivative works. If you do not accept these terms and conditions, do not
use, modify or distribute the Software.

3. RESTRICTIONS ON COPYING, DISTRIBUTION AND USE
The Software may be copied and distributed with or without modifications
in source code and object code form and may be used for commercial and
non-commercial purposes provided that the following restrictions are met:
i. Distribution of the Software is prohibited if any payment is made in
connection with such distribution. You may only charge a reasonable fee
to cover the costs of copying and redistribution;
ii. Bundling the Software with a commercial product or using it to
provide commercial services is prohibited if your product or service
explicitly depends on the Software to be able to operate or function.
You may use the Software without modifications to provide commercial
services or to bundle it with your product provided that your service or
product can also operate or function without the Software.
A commercial license is available if you wish to incorporate the Software
into your product or service which explicitly depends on the Software to
be able to operate or function.

4. RESTRICTIONS ON MODIFICATION AND DERIVATIVE WORKS
The Software may be modified and derivative works may be distributed only
under the terms of this license with the following restrictions:
i. Any modifications and enhancements to the Software, including any newly
developed scripts, libraries, modules that depend on the Software, are
considered derivative works (“Derivative Work”).
ii. If you have modified the Software or created Derivative Work, you
must cause the work to carry prominent notices stating that you have
modified the Software's files and the date of any change. In each source
file that you have modified, you must include a prominent notice that you
have modified the file, including your name, your e-mail address (if
any), and the date and purpose of the change;
iii. All Derivative Works must be made public in source code form by
making it accessible for download over the internet. You must also notify
Licensor about the Derivative Work in e-mail;
iv. All Derivative works must be distributed with an unmodified copy of
this License;
v. By creating a Derivative Work, you assign all copyrights relating to
the modifications to Licensor. You acknowledge that Licensor will own all
copyrights and Licensor may use and distribute the Derivative Work to
third parties under different terms from that of this License.

5. NO WARRANTIES
The Software is provided “AS IS” and Licensor makes no warranty as to its
use, performance, or otherwise. To the maximum extent permitted by
applicable law, Licensor disclaims all other representations, warranties,
and conditions, express, implied, statutory, or otherwise, including, but
not limited to, implied warranties or conditions of merchantability,
satisfactory quality, fitness for a particular purpose, title, and
non-infringement. The entire risk arising out of use or performance of
the Software remains with you.

6. LIMITATION OF LIABILITY
This limitation of liability is to the maximum extent permitted by
applicable law. In no event shall Licensor be liable for any costs of
substitute products or services, or for any special, incidental,
indirect, or consequential damages whatsoever (including, without
limitation, damages for loss of business profits, business interruption,
or loss of business information) arising out of the use or inability to
use the Software, even if Licensor has been advised of the possibility of
such damages. In any case, Licensor's entire liability arising out of
this Agreement shall be limited to the greater of the amount actually
paid for the Software; provided, however, that if you have entered into a
Technical Services Support Agreement, Licensor's entire liability
regarding support services shall be governed by the terms of that
agreement.
tools\nxlog-ce-2.10.2150.msi
md5: AB690FAE35C361F596A6A14CD7157E2E | sha1: 1814F8A5AA240413FE6172E44021FB2EE712FA78 | sha256: DCDDD2297C4FAD9FDEAA36276D58317A7EA1EFCD6851F89215A7231CDA6BA266 | sha512: 41E052F8D08099EECCCA9F8A78D72BA2A2EF88C67F2E046B3F33AF6809C0271BAF82C2819609ACC7020DC8420CDE337C096F7E12A9B4AE555645DFB5B3C961C5
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
 
MD5 checksum for embedded binary should be the same as for binary on nxlog site (https://nxlog.co/system/files/products/files/348/nxlog-ce-2.10.2150.msi): ab690fae35c361f596a6a14cd7157e2e

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.

Version Downloads Last Updated Status
NXLog Community Edition 2.10.2102 935253 Thursday, July 5, 2018 Approved
nxlog 2.9.1716 67338 Wednesday, July 6, 2016 Approved
nxlog Community Edition 2.9.1504 7687 Monday, February 29, 2016 Approved
nxlog 2.8.1248 14347 Tuesday, September 30, 2014 Approved
nxlog 2.7.1191 938 Thursday, March 13, 2014 Approved
nxlog 2.6.1131 435 Wednesday, November 6, 2013 Approved
nxlog 2.5.1089 451 Monday, August 19, 2013 Approved

2018-05-03 2.10.2102

  • Implemented Listen mode for om_tcp which enables clients to connect to it.

2016-07-05 2.9.1716

  • Added a workaround for the 256 source limit in the autogenerated QueryXML in im_msvistalog.
  • Added a workaround for a possible windows bug when im_msvistalog was giving "EvtNext failed with error 1734: The array bounds are invalid."
  • Prevent loss of unprocessed data in im_file buffers upon restart.
  • A leap-year bug was present when parsing dates without a year i.e. Feb 29 showed up as 2016-03-01.
  • Fixed an issue in im_msvistalog that could cause a random crash with custom application logs.
  • Fixed apr_pollset_poll and "unexpected data from server" errors in om_http when the remote server sent fragmented data.
  • im_file now properly updates the file position after each read, not only on EOF.
  • Fixed a reconnection/response timeout issue in om_http.
  • om_http will now attempt to reconnect on all errors.
  • Added a PollInterval directive to im_dbi.

This package has no dependencies.

Discussion for the NXLog Community Edition Package

Ground Rules:

  • This discussion is only about NXLog Community Edition and the NXLog Community Edition 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 NXLog Community Edition, 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