Operations | Monitoring | ITSM | DevOps | Cloud

Sentry’s newest features provide both macro- and micro-level perspective of trends in your errors and application’s health. They’re great — you’ll see.

Elasticsearch, Logstash, and Kibana — the trio better known as Elastic Stack (or ELK, if you prefer a term that is now going out of style), make up a powerful set of tools for searching and analyzing data. Their power derives not just from their technical features, but also the fact that Elastic Stack is an open source platform that anyone can download and set up anywhere.

What an amazing first week! I’ve been marketing open source technologies for over 15 years. During that time, I’ve been involved in many new product releases. Nothing comes close to the response we’ve had from k3s – http://k3s.io. Judging by the incredible feedback (including over 4,500 GitHub stars in one week), the release of k3s appears to have landed at exactly the right time.

Elastic Stack Features (formerly X-Pack) is an Elastic Stack extension that bundles security, alerting, monitoring, reporting, and graph capabilities. One could use either all or specific components.

Just to recap, so far our ongoing series about the Istio service mesh we’ve talked about the benefits of using a service mesh, using Istio for application deployments and traffic management, and how Istio helps you achieve your security goals. In today’s installment, we’re going to dig further into monitoring, tracing, and service-level objectives.

Did you ever have your customer success team (if you have the chance to have one!) overwhelmed by customers throught the support chat when facing minor incidents or even major outages, having to update all those worried customers in real time throught dozens of different channels as the engineering team finds out and resolves the issue? Support costs time, energy and money. What if all of your users could all connect to one single status page that would answer all of their questions?

Usually, when you hear us going on about labels here at Tigera, we are mentioning them as targets for selectors for network policies. As a review, you might have a policy that says, “things labeled customerDB=server should allow traffic on 6443 from things labeled customerDB=client” In this example, the labels identify a resource being produced or consumed.