You may get lucky this holiday season with a new 3D printer, either as a gift or something you give yourself as a reward for all your hard work this year. Household 3D printers have made tremendous strides in ease of use and affordability over the last decade.
As an observability provider, we are always confronted with our clients’ goal for faster resolution of problems and better overall performance of their systems. By working on large-scale projects at Logz.io, I see the same main challenge coming up for all: extracting valuable insights from huge volumes of data generated by modern systems and applications.
We’re excited to announce significant improvements to our Archive+Restore capabilities – which enables low-cost long term log storage in AWS S3 or Azure Blob, while providing access to ingest those logs into Logz.io at any time. The first enhancement is Power Search, which will make it faster to restore logs from archived log data in AWS S3 (and soon for Azure Blob) in our Open 360™ platform.
Is all observability data worth the same cost? If you guessed no, then you’d obviously be correct. Anyone familiar with the very nature of gaining targeted observability knows that some data points hold more value than others. Yet, many observability platforms still treat all types of log data the same, and as a result, related costs remain uniform. One of the most persistent observability challenges today is the cost of indexing log data.
To help our customers reduce their overall observability costs, we’re excited to announce the Data Optimization Hub as part of our Open 360™ platform. The new hub inventories all of your incoming telemetry data, while providing simple filters to remove any data you don’t need. Gone are the days of paying for observability data you never use.
Today we’re excited to announce Logz.io Telemetry Collector – an agent that can send logs, metrics, and traces to Logz.io in a single installation as part of our Open 360™ platform. With Telemetry Collector, customers can get started monitoring their services with Logz.io faster than ever by simplifying the data collection process.
Our product strategy this year was relatively simple. Many observability practitioners we spoke with complained that observability was oftentimes slow, heavy, complex, and costly – which can be summed up in our CEO’s recent blog on modern observability challenges. While our customers didn’t report similar challenges, we wanted to further distance ourselves from this typical observability experience.
Today, I’m thrilled to announce the introduction of Logz.io Open 360™. This is a major step in our journey. Open 360 is a unified platform for modern engineering teams requiring end-to-end observability across logs, metrics and traces—delivered in an intuitive user interface. Open 360™ is specifically designed to enable engineers to have deep monitoring and insights into distributed systems.
What’s the ultimate goal of bringing observability into an organization? Is it just to chase down things when they’re broken and not working? Or can it be used to truly enable developers to innovate faster? That’s a topic I recently discussed with David Ostrovsky, a software engineer at Meta, the parent company of social media networks Facebook and Instagram among others. He was my guest on the most recent episode of the OpenObservability Talks podcast.
OpenSearch was created by the community for the community to continue to keep an open-source alternative to ElasticSearch and Kibana. The project has been hard at work for the last 1.5 years building, launching and iterating on this important initiative. Some remarkable milestones have been achieved, including over 5,800 stars on GitHub with 19 different community-led projects.
