Post
March 11, 2024

Flying through Blind Spots

By
Tim Nichols

TL;DR: Flightcrew helps teams catch configuration issues before they affect production, customers, or budgets. This is something your observability tool can’t do.

When we’re speaking with CTOs we often get asked some version of "Wait - [my observability tool] can’t do this?" We love Datadog but trust us, Datadog can’t solve everything. We’re posting a summary of these conversations to clarify what we’re up to.

Observability tools don’t have a technical/semantic understanding of configs. Flightcrew is config-first 

Observability tools pull logs, metrics, and traces from your environment. As of 2024, they don’t have the time or desire to understand the purpose and meaning of the 1000s of configs shaping your environment.

Flightcrew uses a semantic configuration database and machine learning to surfaces insights like: 

  • Hey, if you update X, you need to compensate by changing Y as well

  • Z is going to expire in 30 days, so you’ll need to update A and B before then

  • You'll be bottlenecked if traffic increases by 10% without adjusting Q

You might recognize these problems and workflows from the security realm. Flightcrew helps infra and platform teams address reliability, scaling, and cost issues with a similar workflow. 

Observability tools help you find & understand problems, Flightcrew recommends solutions 

Observability tools are conservative about putting technology and insights in the production path. This affects everything from integration design to product strategy. It makes sense - observability vendors need to cover a huge footprint and they can’t provide an opinion on everything they cover. 

At Flightcrew, we make honest, transparent recommendations for how to solve a small, but growing number of infrastructure problems and risks. We know you’re busy and don’t want to spend any your time updating configs; if we think you should tune your Redis instance or update KEDA scalers, we’ll just tell you. Rarely is this rocket science, in 2024 it’s about scaling time and insights.

Observability monitors production assets. Flightcrew analyzes assets before they hit production and before they break.

We think 2024 would be slightly less stressful if engineers could understand whether a config state was right for production before you deploy it.

Flightcrew builds a model of optimal settings for your infrastructure and integrates these insights into your native workflow. Flightcrew analyzes your PRs and talks with you in Slack.

In summary: Flightcrew won’t replace your observability tool (we actually integrate with it). Flightcrew uses observability data, documentation, and experimentation data to make opinionated recommendations on how to keep your infrastructure strong and cheap.

Post
March 11, 2024

Flying through Blind Spots

By
Tim Nichols

TL;DR: Flightcrew helps teams catch configuration issues before they affect production, customers, or budgets. This is something your observability tool can’t do.

When we’re speaking with CTOs we often get asked some version of "Wait - [my observability tool] can’t do this?" We love Datadog but trust us, Datadog can’t solve everything. We’re posting a summary of these conversations to clarify what we’re up to.

Observability tools don’t have a technical/semantic understanding of configs. Flightcrew is config-first 

Observability tools pull logs, metrics, and traces from your environment. As of 2024, they don’t have the time or desire to understand the purpose and meaning of the 1000s of configs shaping your environment.

Flightcrew uses a semantic configuration database and machine learning to surfaces insights like: 

  • Hey, if you update X, you need to compensate by changing Y as well

  • Z is going to expire in 30 days, so you’ll need to update A and B before then

  • You'll be bottlenecked if traffic increases by 10% without adjusting Q

You might recognize these problems and workflows from the security realm. Flightcrew helps infra and platform teams address reliability, scaling, and cost issues with a similar workflow. 

Observability tools help you find & understand problems, Flightcrew recommends solutions 

Observability tools are conservative about putting technology and insights in the production path. This affects everything from integration design to product strategy. It makes sense - observability vendors need to cover a huge footprint and they can’t provide an opinion on everything they cover. 

At Flightcrew, we make honest, transparent recommendations for how to solve a small, but growing number of infrastructure problems and risks. We know you’re busy and don’t want to spend any your time updating configs; if we think you should tune your Redis instance or update KEDA scalers, we’ll just tell you. Rarely is this rocket science, in 2024 it’s about scaling time and insights.

Observability monitors production assets. Flightcrew analyzes assets before they hit production and before they break.

We think 2024 would be slightly less stressful if engineers could understand whether a config state was right for production before you deploy it.

Flightcrew builds a model of optimal settings for your infrastructure and integrates these insights into your native workflow. Flightcrew analyzes your PRs and talks with you in Slack.

In summary: Flightcrew won’t replace your observability tool (we actually integrate with it). Flightcrew uses observability data, documentation, and experimentation data to make opinionated recommendations on how to keep your infrastructure strong and cheap.

Post
March 11, 2024

Flying through Blind Spots

By
Tim Nichols

TL;DR: Flightcrew helps teams catch configuration issues before they affect production, customers, or budgets. This is something your observability tool can’t do.

When we’re speaking with CTOs we often get asked some version of "Wait - [my observability tool] can’t do this?" We love Datadog but trust us, Datadog can’t solve everything. We’re posting a summary of these conversations to clarify what we’re up to.

Observability tools don’t have a technical/semantic understanding of configs. Flightcrew is config-first 

Observability tools pull logs, metrics, and traces from your environment. As of 2024, they don’t have the time or desire to understand the purpose and meaning of the 1000s of configs shaping your environment.

Flightcrew uses a semantic configuration database and machine learning to surfaces insights like: 

  • Hey, if you update X, you need to compensate by changing Y as well

  • Z is going to expire in 30 days, so you’ll need to update A and B before then

  • You'll be bottlenecked if traffic increases by 10% without adjusting Q

You might recognize these problems and workflows from the security realm. Flightcrew helps infra and platform teams address reliability, scaling, and cost issues with a similar workflow. 

Observability tools help you find & understand problems, Flightcrew recommends solutions 

Observability tools are conservative about putting technology and insights in the production path. This affects everything from integration design to product strategy. It makes sense - observability vendors need to cover a huge footprint and they can’t provide an opinion on everything they cover. 

At Flightcrew, we make honest, transparent recommendations for how to solve a small, but growing number of infrastructure problems and risks. We know you’re busy and don’t want to spend any your time updating configs; if we think you should tune your Redis instance or update KEDA scalers, we’ll just tell you. Rarely is this rocket science, in 2024 it’s about scaling time and insights.

Observability monitors production assets. Flightcrew analyzes assets before they hit production and before they break.

We think 2024 would be slightly less stressful if engineers could understand whether a config state was right for production before you deploy it.

Flightcrew builds a model of optimal settings for your infrastructure and integrates these insights into your native workflow. Flightcrew analyzes your PRs and talks with you in Slack.

In summary: Flightcrew won’t replace your observability tool (we actually integrate with it). Flightcrew uses observability data, documentation, and experimentation data to make opinionated recommendations on how to keep your infrastructure strong and cheap.

Engineering teams use Flightcrew to make
every pull request more reliable

Engineering teams use Flightcrew to make every pull request more reliable

Engineering teams use Flightcrew to make every pull request more reliable