We recently introduced Catalog: the connected map of everything in your organization. In the process of building Catalog as a feature, we’ve also been building out the content of our own catalog. We'd flipped on the feature flag to give ourselves early access, and as we went along, we used this to test out the various features that Catalog powers.
As you may have already seen, we’ve recently released a Catalog feature at incident.io. While designing and building it, we took an approach that’s a tangible departure from a traditional service catalog. Here’s how we’re different, and why.
This morning, Microsoft Teams suffered an outage with users unable to access Microsoft Teams unless they were using the Teams client. Editor’s Note: This outage lasted about 2 hours including the time to roll out a fix, Exoprise customers knew of the issue around 35 minutes before Microsoft. Exoprise proactive monitoring first detected the outage in North America starting at 7:20 AM EDT.
Monitoring is all about data. When you implement a monitoring tool, you have to make sure that the monitoring software can handle data. Today, data flows at high speeds and in large volumes. Data also comes in diverse forms, which increases the complexity of data ingestion. Because of this, monitoring solution providers promote, among others, their data processing capacities. If a monitoring platform can handle large and diverse data that comes in at a high velocity, it becomes a big advantage.
A containerized approach to software deployment means you can deploy at scale without having to worry about the configuration of each unit. In Kubernetes, clusters do the heavy lifting for you—they’re the pooled resources that run the pods that hold your individual containers. You can divide each cluster by namespace, which allows you to assign nodes (ie the machine resources in a cluster) to different roles or different teams. Resource quotas limit what each namespace can use.
In today’s digital landscape, the aviation industry faces increasingly sophisticated cyber threats that can compromise the safety and security of critical systems. To combat these challenges, the Transportation Security Administration (TSA) has implemented new cybersecurity requirements. In this blog post, we’ll explore how Teneo, in collaboration with Akamai Guardicore, can help aviation organizations meet these requirements and strengthen their cybersecurity defenses.
This post was written by Pete Osah, a software developer who is familiar with web technologies, passionate about new software technologies, and keen on developing ways to pass knowledge to others in a simple manner. Thanks to new technologies, developers can release software and features to production at a faster pace and with greater efficiency. But maintaining software dependability and integrity requires having the necessary tools in place.
