Skip to content
Log Insight Export
Python
Branch: master
Clone or download
alanjcastonguay Merge pull request #33 from vmware/topic/export-format-converter-4
Convert from export-json format to ingestion-api json format
Latest commit 8809029 Jan 5, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
loginsightexport Convert from export-json format to ingestion-api json format Jan 4, 2018
tests Convert from export-json format to ingestion-api json format Jan 4, 2018
.gitignore
.travis.yml
CONTRIBUTING.md Update CONTRIBUTING.md Feb 2, 2017
LICENSE.txt Initial commit Jan 27, 2017
MANIFEST.in
NOTICE.txt
README.md
exportshare.png
loginsightexport.spec
requirements.txt Log Insight export utility Jan 27, 2017
setup.py Convert from export-json format to ingestion-api json format Jan 4, 2018
tox.ini

README.md

A command-line exporter of log events in VMware vRealize Log Insight. Exceed the 20k UI limit. Write local files.

loginsight-export

Installation

  1. Open a command prompt.
  2. pip install loginsight-export
  3. loginsight-export -h

Usage

  1. In Log Insight Interactive Analytics, perform a query of arbitrary complexity and size.
  2. Use the Share button to generate a short url for the current query.
  3. loginsight-export https://loginsight.example.com/s/123456

Overview

VMware vRealize Log Insight supports exporting query results to a file in the UI. However, a single export is limited to 20k results. To export more results, an operator can execute a sequence of queries with non-overlapping time-ranges, each of which contained less than 20k. As scale increases, this becomes cumbersome. This utility starts with a single UI-driven time-range, recursively breaks the full range down into sequential <=20k-sized chunks, and executes an export for each chunk.

Prerequisites

  • Built on Requests.
  • Python 3.4 or higher.
  • Uses tox, pytest, requests-mock for testing.

Secure Connections

The exporter verifies a remote server's certificate against your CA trust chain by default. If Log Insight is using a valid certificate that's not trusted by your local machine (e.g., self-signed), use the --save command-line argument to write a local PEM file and --verify to trust it. The certificate's integrity is still verified.

If Log Insight is using the auto-generated certificate with a common name that doens't match Log Insight's hostname, the request will fail:

loginsightexport: error: The remote SSL certificate isn't trusted: hostname '192.168.3.30' doesn't match 'VMware vCenter Log Insight'

It's always recommended to use real certificates. To bypass this check in a test environment, use the --insecure command-line argument.

Contributing

The loginsight-export project team welcomes contributions from the community. If you wish to contribute code and you have not signed our contributor license agreement (CLA), our bot will update the issue when you open a Pull Request. For any questions about the CLA process, please refer to our FAQ. For more detailed information, refer to CONTRIBUTING.md.

License

Distributed under the Apache Version 2.0 license

You can’t perform that action at this time.