Publish Log From Naked MuleSoft Deployment to Logz.io

Agenda

  • Introduction.
  • What is Logz.io ?
  • Naked deployed MuleSoft configuration to send log to Logz.io.

Introduction

MuleSoft Feature

MuleSoft supports configuration and dependencies in log4j to publish logs to logz.io from CloudHub and Naked Mulesoft deployment.

About Logz.io 

Logz.io provides a cloud-based log analysis service which is based on the open source log analysis platform — the ELK Stack (Elasticsearch, Logstash, Kibana).

Logging Istio with ELK and Logz.io

Load balancing, traffic management, authentication and authorization, service discovery — these are just some of the interactions taking place between microservices. Collectively called a “service mesh,” these interconnections can become an operations headache when handling large‑scale, complex applications.

Istio seeks to reduce this complexity by providing engineers with an easy way to manage a service mesh. It does this by implementing a sidecar approach, running alongside each service (in Kubernetes, within each pod), and intercepting and managing network communication between the services. Istio can be used to more easily configure and manage load balancing, routing, security, and the other types of interactions making up the service mesh.

Monitoring Microsoft Azure With Logz.io

Microsoft Azure has long proven it’s a force to be reckoned with in the world of cloud computing. Over the past year, Azure has made some significant steps in bridging the gap with AWS by offering new services and capabilities as well as competitive pricing. 

A growing number of our users are Azure fans, and so we’re happy to introduce a new Logz.io integration for Azure as well as premade dashboards for monitoring different Azure resources!

Server Monitoring With Logz.io and the ELK Stack

In a previous article, we explained the importance of monitoring the performance of your servers. Keeping tabs on metrics such as CPU, memory, disk usage, uptime, network traffic, and swap usage will help you gauge the general health of your environment as well as provide the context you need to troubleshoot and solve production issues.

In the past, command line tools, such as top, htop, or nstat, might have been enough, but in today’s modern IT environments, a more centralized approach for monitoring must be implemented.