Skip to main content

BASH POST ElasticSearch

Looking for a way to log messages to an Elasticsearch instance, I searched and found that this would be my preferred one.

Prerequisites are to have jq and curl installed.

Write a function elk_log():

elk_log(){
    # Default configuration
    ELK_HOST="elasticsearch.rktmb.org"
    ELK_PORT=9200
    ELK_IDX="mihamina-database"

    # Overridden if ENV vars set:
    if [ -n "$GW_HOST" ]; then	ELK_HOST=$GW_HOST; fi
    if [ -n "$GW_PORT" ]; then	ELK_PORT=$GW_PORT; fi
    TSTAMP=$( date --iso-8601=sec )

    curl -H "Content-Type:application/json" \
	 -X POST --silent \
	 --data "$( jq -n \
		      --arg tstamp "$TSTAMP" \
		      --arg message "$1" \
		      '{timestamp: $tstamp, message: $message}' )" http://${ELK_HOST}:${ELK_PORT}/${ELK_IDX}/_doc
}

Then call this with:

#[...]
elk_log "MIHAMINA DATA STRUCTURE BEGIN"
#[...]
elk_log "MIHAMINA DATA STRUCTURE END"
#[...]

Thanks to https://stackoverflow.com/a/48470227  

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

emacs29 intelephense

Emacs 29 and PHP Intelephense I use to use Emacs and PHP Intelephense for PHP development. I recently upgraded to Emacs 29 and PHP Intelephense stopped working. I found a solution on Reddit Based on that, I rewrote my .emacs file to use eglot instead of lsp-mode, and this is the result. (use-package eglot :ensure t) (add-hook 'php-mode-hook 'eglot-ensure) (use-package php-mode :ensure t :mode ("\\.php\\'" . php-mode)) (add-to-list 'auto-mode-alist '("\\.php$" . php-mode)) (provide 'lang-php) (use-package company :ensure t :config (setq company-idle-delay 0.3) (global-company-mode 1) (global-set-key (kbd "M- ") 'company-complete)) (require 'eglot) (add-to-list 'eglot-server-programs '((php-mode :language-id "php") . ("intelephense" "--stdio" :initializationOptions (:licenseKey "98989898989898989898"

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM