Operations | Monitoring | ITSM | DevOps | Cloud

As well as being a search engine, Elasticsearch is also a powerful analytics engine. However, in order to take full advantage of the near real-time analytics capabilities of Elasticsearch, it is often useful to add structure to your data as it is ingested into Elasticsearch. The reasons for this are explained very well in our schema on write vs. schema on read blog post, and for the remainder of this blog series, when I talk about structuring data, I am referring to schema on write.

There’s no getting around the prevalence of heterogeneous tools in IT operations and DevOps. Teams have built up ecosystems of tools over time for different infrastructure, workflows and applications – and while some of them are outdated or duplicitous – plenty still serve a useful purpose in the enterprise. Yet unfortunately tool sprawl adds to the complexity of monitoring a hybrid or multi-cloud environment.

I am spending a considerable amount of time recently on distributed tracing topics. In my previous blog, I discussed different pros and cons of various approaches to collecting distributed tracing data. Right now I would like to draw your attention to the analysis back-end: what does it take to be good at analyzing transaction traces?

Nexthink’s Chief Product Officer, Samuele Gantner, spoke recently with Digitalisation World, a popular tech news company to discuss the next generation of our Experience Platform. IT departments around the world are under considerable stress nowadays but there are several fast and practical solutions available in the Nexthink platform that our customers are using to help support their remote workers and flexible work environments.

SMEs struggle with keeping business processes running smoothly, from managing workflows to keeping records on sales and customer interactions. However, small businesses can make their life in business smarter and easier by integrating automation tools. Business automation is fast transforming how brands carry out their operations. In essence, the size of business does not matter when it comes to automation.

Monitoring the state of DevOps, multi-cloud, microservices and data centre environments is no easy task. You can’t manage what you can’t see. Gaps in your monitoring capability leave your enterprise vulnerable to catastrophic, customer impacting infrastructure blind-spots.

I recently spoke with Alex Skrivseth, the Operations Manager at The Shed App, and discovered how he’s using InfluxDB to monitor the current levels of gas and diesel at various gas stations. Simply by extracting IoT sensor data, he has been able to provide valuable previously inaccessible data to fuel truck drivers.

This article will focus on debugging JavaScript code within Microsoft Edge Developer Tools. The Edge DevTools are a powerful toolset built into the Edge browser on Microsoft Windows 10. The DevTools are also available as a standalone app to download from the Microsoft Store, if one prefers to run them separately from Edge itself. We’ll be using Raygun Crash Reporting to find the stack trace and the line of code the error occurred on. You can sign up for a free 14-day trial here.

Over the last few decades, some firms have worked hard to hire the right people and develop the right processes. However, those achievements have not translated into bottom-line growth. A more detailed examination of that matter shows that the issue lies somewhere in productivity.

All storage devices, whether on-premises or in the cloud, are used to store or maintain data in a server. To organize files based on usage and perform read/write operations, the disk is divided into separate portions called partitions. A partition can contain the entire disk space or some of it. Disk usage gives the amount of space used by the storage device to read/write an operation.