Elasticsearch Typed Keys In Elasticsearch Java Client This is not the first time I have encountered Elastic clients returning different data formats, but this one is just truly baffling. The Java API serializes its information with "typed keys" so that it can deserialize its own data internally. These types
Elasticsearch Elasticsearch REST API vs. JavaScript Client I was surprised to find out that there are differences between a direct REST call in Elastic and the exact same call in the Elastic JavaScript client. The endpoint: _search Curling to REST requires the sort portion of the request body to look like
Grafana Non Legacy Form Data Source Plugin Grafana Grafana 7.5.x As previously mentioned, the tutorial for Grafana data source plugin development is all over the place. Even in the latest version of Grafana (8.x), the tutorial shows this as the way to write the query editor form: <div
JavaScript Using TLS In Your Grafana Datasource In the previous post, we discussed how to write your own custom Grafana datasource plugin. We recently upgraded our backend to move from a username/password to certificate mode. This necessitated updating the datasource plugin to be able to make a request to the
JavaScript Writing a datasource plugin for Grafana Grafana version 7.x. As of this writing, the tutorial from Grafana on how to write datasource plugin is completely broken. I wasted an entire afternoon trying to decipher what they were saying in the tutorial versus the rest of the documentation. Executive summary:
JavaScript Passing a Client Certificate in webpack proxy I really like create-react-app. It hides away all of the configuration I don't really need when I am prototyping. An interesting use case I had recently was an application that needs client authentication. I was surprised to find out that if you started your