We are proud to announce the launch of direct dashboard uploads with Logz.io. These new metrics dashboard templates are available for 25 different tools and more to come. Each of these templates is now available to Logz.io customers and covers the gamut of popular monitoring tools used by DevOps teams. Some of these tools also include multiple options. The process is simple. Head into the Logz.io app and head to your metrics account.
Logz.io is proud to announce a slew of new integrations via Telegraf. Logz.io utilizes Prometheus in its product, but aims to support compatibility across common DevOps tools. A number of our customers, and the community in general, are strong users of Telegraf and its companion apps in the TICK Stack (which includes InfluxDB). Telegraf is not as popular as Prometheus, but it’s a strong element in the DevOps toolbox.
Our first tutorial gave a general introduction to OpenSearch installation and configuration. We recently also published a comparative introduction for OpenSearch queries (and how they parallel or contrast with Elasticsearch). Now, we’ll continue that series with an intro to OpenSearch clusters. This is a very simple tutorial with straight-forward examples, but we will try to cover some detail and common advanced settings.
In this tutorial, we will go through a working example of a Ruby application auto-instrumented with OpenTelemetry. To keep things simple, we will create a basic “Hello World” application, instrument it with OpenTelemetry’s Ruby client library to generate trace data and send it to an OpenTelemetry Collector. The Collector will then export the trace data to an external distributed tracing analytics tool of our choice.
Back in June, we announced the Public Beta for Logz.io’s New Lookz – which is a new UI that completely changes the way users navigate across Logz.io products and features. The Public Beta gave users the option to toggle between the old and new UIs to see which one they liked better. And the answer from our users was as clear as it could be.
If you’re a DevOps practitioner working in a Microsoft-centric environment, you’ll be pleased to learn that Logz.io recently added support for the popular Teams communications hub to help broadcast pressing alerts and other monitoring data. The integration comes on the heels of making the Logz.io platform directly available from within the Azure Console and expands organizations’ abilities to communicate and share notifications about everything from log data to security events.
OpenSearch has evolved rapidly since its fork from the source code of the last truly open source version of Elasticsearch. So far, the community’s work has focused on removing proprietary code from Elastic, including a number of things that were never purely open source themselves. These include some aspects of the querying languages and capabilities of Elasticsearch.
Cloud monitoring and observability can involve all kinds of stakeholders. From DevOps engineers, to site reliability engineers, to Software Engineers, there are many reasons today’s technical roles would want to see exactly what is happening in production, and why specific events are happening. However, does that mean you’d want everyone in the company to access all of the data?
The ultimate success of any security monitoring platform depends largely on two fundamental requirements – its ability to accurately and efficiently surface threats and its level of integration with adjacent systems. In the world of SIEM, this is perhaps more relevant than any other element of contemporary IT security infrastructure.
