The ability to access the internal state of your application ecosystem is critical to optimizing your applications and the experience of your users. Elastic Cloud on Microsoft Azure gives you access to Elastic Observability, allowing you to monitor your infrastructure and see how every signal interrelates by utilizing a wide variety of resources that can be deployed in minutes.

When we look at information, numbers, percentages, statistics, we tend to have an easier time understanding and interpreting them if they’re also represented by corresponding visual cues. Kibana Canvas is a tool that helps us present our Elasticsearch data with infographic-like dashboards – fully visual, dynamic, and live.

If you’re reading this, you have probably been convinced that taking on Kotlin for your mobile application is the most sensible choice. Now that you’ve come to this decision, it’s imperative to know what you need to do to stay on top of your monitoring and logging. Like with any application or system, they are essential, cornerstone qualities of any successful project.

We’re pleased to announce that we’ve recently launched our improved audit log feature and have rolled this out to users across all of Logit.io’s operating regions. The audit log is visible on both account and individual Stack level.

This post aims to provide a very simple beginner’s guide to Jaeger + OpenTracing instrumentation for Go applications (the terms “application” and “service” is used interchangeably in this document) via a working example. If you are new to instrumentation, I recommend that you first read this post for a practical introduction to instrumentation for Jaeger and OpenTracing. You can also get more info on using logs in Go.