To complement distributed tracing, runtime metrics, log analytics, synthetic testing, and real user monitoring, we’ve made another addition to the application developer’s toolkit to make troubleshooting performance issues even faster and simpler. Today, we’re excited to introduce Profiling—an always-on, production profiler that enables you to continuously analyze code-level performance across your entire environment, with minimal overhead.
I don’t know how the term “shaving the yak” caught on, but I’m willing to embrace it for all of its weirdness and meaning. We all spend a lot of time on tasks that don’t directly relate to some meaningful objective. Sometimes they’re useful, but far removed from the impact they deliver. Some tasks, such as setting up Trello to better manage my blog posts, can result in hunting down some obscure integrations with IFTT or Zapier and getting those to work.
AWS offers a variety of services to solve specific needs. There are some core services, like EC2 and VPC, that let you create an infrastructure for your applications that scales easily. But if you’re new to AWS and also new to infrastructure, you might need to invest some time reading before you deploy your application to AWS. I remember my first time using AWS; the sysadmin explained to me what systems we were using in AWS to run the company’s main application.
Just to make sure we’re on the same page before we begin — platform teams reduce cognitive load for developers and make it easier to ship new features. They can have an enormous impact on your organization. Whether that impact is positive or negative is up to the managers, developer teams, and organization as a whole. Here’s a quick overview on what not to do.
As companies and teams become more and more distributed, communication only becomes more important. For organizations that deal with finance matters, this is only more true. There is no room for miscommunications and distractions when there are large amounts of money being transferred and worked with. One client came to us seeking a solution to their management of tickets, along with some sensitivity to permissions, communications, and the ability to track change.
Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. In the first Five worthy reads of this year, we’ll explore data democratization in detail, from its definition to its pros and cons, and provide some ways to use it for data empowerment.
Data destruction is an aggressive attack technique observed in several nation-state campaigns. This technique under MITRE ATT&CK 1485, describes actions of adversaries that may “..destroy data and files on specific systems or in large numbers on a network to interrupt availability to systems, services, and network resources. Data destruction is likely to render stored data irrecoverable by forensic techniques through overwriting files or data on local and remote drives”.
Does one or more of the following personas describe you? If you fit one of those personas, you are in luck because I’m happy to tell you about some new Splunk integrations with Visual Studio Code in this blog.
SmartBear conducts a number of surveys each year, many of which we’re proud to see be referenced by data analysts and journalists throughout the tech industry. My personal favorite survey report that we put out is the Software Testing Survey Insights Report.
In today’s world, we enjoy incredible mobility that our ancestors could only dream of. In a matter of hours or, at most, days, we can go from one continent to another. At the same time, our lives depend on the security of all sorts of our private data: from our credit card information to our browsing habits. But if at our homes we can be sure that we have taken sufficient security measures and protected our systems, things get muddier when we travel.
Source control, aka version control, is the method of tracking and managing changes to software code. Source Control Management (SCM) systems offer a running history of code changes and can be particularly helpful for teams of developers making changes to the same files. As a critical aspect of responsible software development, source control helps developers track code changes, see complete revision history, and revert back to a previous version of a project if needed.
Starting April 21, 2020, all requests to Elasticsearch Service on Elastic Cloud must use HTTP over TLS (HTTPS) with support for TLS 1.2. We’ve decided to make this change in the best interest of our users so we can ensure the security of data in transit and stay up to date with modern encryption, security protocols, and practices.
