Operations | Monitoring | ITSM | DevOps | Cloud

We are delighted to announce our new PagerDuty integration for Salesforce Cloud. This integration empowers Customer Service, Engineering, and IT teams to proactively resolve customer issues in real time by improving communication and collaboration.

This is the story of how I used Honeycomb to troubleshoot redis/redis-rb#924 and discovered a surprising workaround.

This post is the second in our Kubernetes observability tutorial series, where we explore how you can monitor all aspects of your applications running in Kubernetes, including: We’ll cover using Elastic Observability to ingest and analyze container metrics in Kibana using the Metrics app and out-of-the-box dashboards.

Elasticsearch powers search experiences for so many tools and apps used today, from operational analytics dashboards to maps showing the closest restaurants with patios so you can get out of the house. And in all of those implementations, the connection between application and cluster is made via an Elasticsearch client. Optimizing the connection between the client and the Elasticsearch cluster is extremely important for the end user’s experience.

When making purchasing decisions, organizations must consider a vendor’s product pricing, promised benefits and level of customer service. Thorough vendor evaluation tends to result in successful investments, allowing organizations to reap the benefits of their newly acquired products without buyer’s remorse. Unfortunately, some buyers dismiss the importance of personal information security and how the vendor promises to protect user data.

A while ago, we covered the invocation (trigger) methods supported by Lambda and the integrations available with the AWS catalog. Now we’re launching a series of articles to correlate these integration possibilities with common serverless architectural patterns (covered by this literature review). In Part I, we will cover the Orchestration & Aggregation category. Subscribe to our newsletter and stay tuned for the next parts of the series.

This article was originally published in New Stack. More and more companies have gone remote with surprising benefits — a trend that has been building for years. A survey by Global Workplace Analytics and FlexJobs indicates that remote work has grown 91% over the last 10 years, and 159% over the last 15 years. The COVID-19 pandemic has elevated the relevance of remote work (including remote IT operations) to a new level.

Cybersecurity has always been an evolving challenge for IT teams—even before the pandemic and subsequent mass exodus to the home office. At the Protect & Streamline Summit for IT Leaders, experts from the IT and cybersecurity space came together to share advice for IT leaders scrambling to contend with a new set of business risks. Read on for key takeaways or access all session recordings for a deeper dive.

Unless you’ve been living under a rock you are probably familiar with the recent Shadow Brokers data dump of the Equation Group tools. In that release a precision SMB backdoor was included called Double Pulsar. This backdoor is implemented by exploiting the recently patched Windows vulnerability: CVE-2017-0143. For detection, we are going to first focus on the backdoor portion of the implant, hunting for traces left behind on the network.

At Cloudsmith, you will often hear us refer to our mantra of “Automate Everything”. It a quest that we never deviate from, and we believe that anything that can be automated, should be automated. With that in mind, we would like to show you how simple it is to integrate a Cloudsmith repository with your Buildkite pipeline, and automate the pushing of your build artifacts into your own private repository for further CI/CD steps or even as a source for your global distribution needs.