Why is this awesome?

Now that I can use docker directly from Jenkins jobs, it means I can setup cron jobs through jenkins just with configuration. Since one of docker sweet point is the ability to run CLI tools without any more setup that downloading an image, I now can setup nightly elastic/curator cron jobs just from Jenkins interface without the initial overhead of environnement setup.

I get fail build notifications directly from Hipchat (always be proactively alerted when something goes wrong!), traceability (who started the job) and of course I can reuse my Jenkins authorization setup for cron job as well. Thus no need to setup something like Rundeck when Jenkins already handles the feature set I want!

⚡️ Receive a weekly recap' of the best libraries and projects I found on the web

I had to handle a 2 month old issue related to ElasticSearch. A feature I did not know from one of our large monolithic application at iAdvize was not working anymore. Instead of looking directly at thousand lines of code, the fastest way to resolve it was to gather informations related to the issue from outside the app. I had to answer this questions:

Is the ElasticSearch server remotely accessible from the frontend servers?

If it does not, the first thing to do is to bring back the connexion between the two.

Is the ElasticSearch request valid?

If it does not, maybe:

we are doing the request on the wrong indice/alias?

the query body is malformed?

Does it yield results?

If it does not

but we should get some, then either the query is invalid or elasticsearch have an issue

If it does

but from the app point of view we don't get anything

it's related to the app itself and we will have to look at the code

To verify the first 3 points in one shot, I started tcpdump on the ElasticSearch server using the command below: