npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

elasticsearch-cleaner

v2.2.1

Published

Asynchronously prune your Elastic Search indices.

Downloads

14

Readme

Elasticsearch Cleaner

Asynchronously prune your Elasticsearch indices. In the browser, in Node.js or in the command-line interface. Assuming that your indices follow the official recommendation to have one Index per Time Frame. If indices are not conventionally named, then this module/cli tool can't help you.

Motivation

Ability to prune indices is needed to save storage space, or to comply with data protection laws like GDPR.

Installation

Install globally to use it any where within your system.

npm i elasticsearch-cleaner -g

Or install it inside your web project.

npm i elasticsearch-cleaner

Usage

CLI

es-cleaner --url=<...> [--days=30] [--reg-exp=[0-9]{4}-[0-9]{2}-[0-9]{2}$] [--for-real]

Options:

  • --help: Show help
  • --version: Show version number
  • --url or -u: Elasticsearch url, including the port if needed.
    • Required.
  • --days or -d: How old should indices be in order to be deleted?
    • Default: 30 days.
  • --reg-exp or -r: Regex Expression to match the date part of the index name.
    • Default: [0-9]{4}-[0-9]{2}-[0-9]{2}$ (Matches YYYY-MM-DD at the end).
    • A string that will be passed to new RegExp.
  • --for-real: A flag to actually delete the indices. By default the tool doesn't delete anything, it only shows you what it would delete.
    • Required to actually delete the indices.

As JS Module

// ES6 syntax
import ElasticSearchCleaner from 'elasticsearch-cleaner';

// Node.js
const ElasticSearchCleaner = require('elasticsearch-cleaner');

// These arguments are the same ones listed above in the cli explanation.
const url = 'https://elasticsearch:example.com';
const age = 30;
const regexp = '[0-9]{4}-[0-9]{2}-[0-9]{2}$';
const forReal = true;

const elasticSearchCleaner = new ElasticSearchCleaner(url, age, regexp, forReal);

elasticSearchCleaner.exec();

License

MIT