Blog

The logstash configuration can become quite complex. Some hints how to tryout if the configuration is not working.

To send data from a RESTful Webservice, there is the input plugin exec. It executes a command for a defined interval.

Working with logstash on a Windows machine is a little tricky. The curl command exists as Windows binary. Invoking curl gives me a JSON message, that I used for logstash input.

Jolokia is remote JMX with JSON over HTTP. It provides several agents to expose JMX MBeans. OSGi is one of them . Using DropWizard Metrics with the JmxReporter, you can easily access the metrics. If you use the Java EE agent (deploy the jolokia.war to your Java EE application server), it enables you to access the metric under the given MBeans objectName, e.g. The context-root can be simplified to jolokia via the web.xml.

Encrypt.to is a good way to provide (initial) contact with an encrypted email. Just enter the email address of the recipient and if the lookup for a (public) gpg key is successful, you are free to send. There are various service levels from free to enterprise. Quite handy if you have no email client with gpg support or gpg itself around.

If you need to check that a remote host has a socket open, check following example. This example creates a socket at the HTTP port over your custom network proxy. If the proxy requires authentication, you may override the default Authenticator. Keep in mind that it is only an example!

Dealing with data in text files sometimes gives you headaches with file encoding. A tool that helps us overcome our problem is iconv. iconv converts text from one character encoding to another encoding.

For the SSH Authentication the gpgsm package is needed, because we need “scdaemon” = smartcard-daemon

psql has the capability to export the output to files. This is a write-up for it. I got several use cases: