"From my perspective, and I work with some other open source projects, Keep is currently my favorite open source project," Marco shares. "The responsive team and the joyful growth make it stand out." Having used Keep for over a year, Marco appreciates the rapid pace of development. "I'm having a hard time staying on top of the version updates, which is a good thing! And the team handles contributions very well, making it a positive experience."

About JustTrack

JustTrack is a mobile measurement and attribution platform that helps app developers track user behavior, optimize marketing campaigns, and grow their user base through data-driven insights.

The Challenge: Multiple Alert Systems, No Uniformity

Before implementing Keep, JustTrack faced a common but complex challenge in their technical infrastructure: managing alerts from multiple disparate systems.

"We had multiple systems which emit alerts, and they all are widely different from one another," explains Marco, DevOps Engineer at JustTrack. "For example, Sentry, CloudWatch, Prometheus, and more."

This diversity of alert sources created significant operational challenges:

  • Inconsistent alert formatting across platforms
  • Different severity and priority classifications between systems
  • Complex routing rules that required extensive maintenance
  • Significant duplication of effort
  • Alert management that wasn't managed as code
  • Challenges in properly routing alerts to the appropriate teams

JustTrack was using SquadCast for escalation policy and routing, but the lack of uniformity in the alerts required creating numerous expressions and routing rules for each service. "It was a lot of maintenance, a lot of duplication, and it didn't even work really well because it wasn't managed as code. Sometimes someone would forget to update rules, and you'd have suppression rules you didn't set up—just a bad experience," Marco recalls.

The Solution: Keep's Unified Alert Management

JustTrack needed a unified alerting system that could normalize data from different sources and provide a consistent way to handle alerts regardless of their origin. After evaluating their options, Keep stood out as the only solution with the capabilities they needed.

"Keep was the only option that let us achieve a uniformity on the payload and alert side, which helped in all further actions like automation, notification, and escalation," says Marco.

The key capabilities that made Keep the right choice for JustTrack were:

  • Extraction & Mapping: The ability to transform payloads from different providers into a uniform format
  • Standardized Severity/Priority: Normalizing different alert levels across systems
  • Team-Specific Routing: Enabling alerts to be properly directed based on ownership

Implementation: Infrastructure as Code

JustTrack's implementation approach highlights Keep's flexibility:

  • Deployment via Keep's Helm chart within an internal "infrastructure as code" repository
  • Traffic as their entry point instead of NGINX, with custom configurations for their specific needs
  • Configuration management using Keep's Terraform provider to provision all alert configurations, mappings, and workflows
  • MySQL database backend for data persistence

"We have one repository where we mainly configure through Terraform," explains Marco. "With the Terraform provider, we are provisioning all the configuration like mappings, providers, and extraction rules."

Before and After Keep

Before Keep:

  • Multiple entry points for alerts
  • Complex expressions and routing rules for each service
  • High maintenance overhead
  • Inconsistent formatting and priorities
  • Alert management not managed as code
  • Frequent issues with missed alerts or improper routing

After Keep:

  • Reduced to only two entry points for alerts
  • Alert logic handled by Keep
  • Only 8 routing rules (down from dozens)
  • Uniform alert payload format
  • Priority/severity standardization
  • Proper team routing based on ownership
  • Critical alerts (P1) automatically route to specific policies with text/phone notifications

"By handling all the logic on the Keep side for priorities, severity, and ownership, we now only need to define where we want to put alerts in our escalation policies. Everything else is handled directly by Keep," says Marco.

Working with Keep: "My Favorite Open Source Project"

JustTrack's experience working with Keep and its team has been overwhelmingly positive.

"From my perspective, and I work with some other open source projects, Keep is currently my favorite open source project," Marco shares. "The responsive team and the joyful growth make it stand out."

Having used Keep for over a year, Marco appreciates the rapid pace of development. "I'm having a hard time staying on top of the version updates, which is a good thing! And the team handles contributions very well, making it a positive experience."

Looking Ahead: JustTrack's Future with Keep

JustTrack sees Keep becoming increasingly central to their observability and alert management strategy:

  1. More Logic and Automation: Expanding their use of Keep workflows, including LLM integration for automated first-response messages
  2. Platform Independence: Reducing dependencies on other alerting platforms as Keep takes on more functionality
  3. Incident Management: Using deduplication and correlations to work with incidents instead of individual alerts, while maintaining complete visibility of all alert information

"The goal is to reduce noise but still not lose any kind of information, have a timeline, and utilize the incident deduplication or correlations in a way that actually works," explains Marco.

Conclusion

Keep has transformed how JustTrack manages alerts across their complex infrastructure, providing the uniformity and consistency they needed while reducing maintenance overhead. The partnership has been characterized by responsive support and continuous improvement, making Keep a critical component of JustTrack's technical stack.

"What I don't like is that you need more and more software-as-a-service products for all your needs," concludes Marco. "That's a strong point for Keep with its advanced functionality—the more extensive the features get, the better it is for the end user to adjust, do custom things, and build upon it."

"From my perspective, and I work with some other open source projects, Keep is currently my favorite open source project," Marco shares. "The responsive team and the joyful growth make it stand out." Having used Keep for over a year, Marco appreciates the rapid pace of development. "I'm having a hard time staying on top of the version updates, which is a good thing! And the team handles contributions very well, making it a positive experience."

About JustTrack

JustTrack is a mobile measurement and attribution platform that helps app developers track user behavior, optimize marketing campaigns, and grow their user base through data-driven insights.

The Challenge: Multiple Alert Systems, No Uniformity

Before implementing Keep, JustTrack faced a common but complex challenge in their technical infrastructure: managing alerts from multiple disparate systems.

"We had multiple systems which emit alerts, and they all are widely different from one another," explains Marco, DevOps Engineer at JustTrack. "For example, Sentry, CloudWatch, Prometheus, and more."

This diversity of alert sources created significant operational challenges:

  • Inconsistent alert formatting across platforms
  • Different severity and priority classifications between systems
  • Complex routing rules that required extensive maintenance
  • Significant duplication of effort
  • Alert management that wasn't managed as code
  • Challenges in properly routing alerts to the appropriate teams

JustTrack was using SquadCast for escalation policy and routing, but the lack of uniformity in the alerts required creating numerous expressions and routing rules for each service. "It was a lot of maintenance, a lot of duplication, and it didn't even work really well because it wasn't managed as code. Sometimes someone would forget to update rules, and you'd have suppression rules you didn't set up—just a bad experience," Marco recalls.

The Solution: Keep's Unified Alert Management

JustTrack needed a unified alerting system that could normalize data from different sources and provide a consistent way to handle alerts regardless of their origin. After evaluating their options, Keep stood out as the only solution with the capabilities they needed.

"Keep was the only option that let us achieve a uniformity on the payload and alert side, which helped in all further actions like automation, notification, and escalation," says Marco.

The key capabilities that made Keep the right choice for JustTrack were:

  • Extraction & Mapping: The ability to transform payloads from different providers into a uniform format
  • Standardized Severity/Priority: Normalizing different alert levels across systems
  • Team-Specific Routing: Enabling alerts to be properly directed based on ownership

Implementation: Infrastructure as Code

JustTrack's implementation approach highlights Keep's flexibility:

  • Deployment via Keep's Helm chart within an internal "infrastructure as code" repository
  • Traffic as their entry point instead of NGINX, with custom configurations for their specific needs
  • Configuration management using Keep's Terraform provider to provision all alert configurations, mappings, and workflows
  • MySQL database backend for data persistence

"We have one repository where we mainly configure through Terraform," explains Marco. "With the Terraform provider, we are provisioning all the configuration like mappings, providers, and extraction rules."

Before and After Keep

Before Keep:

  • Multiple entry points for alerts
  • Complex expressions and routing rules for each service
  • High maintenance overhead
  • Inconsistent formatting and priorities
  • Alert management not managed as code
  • Frequent issues with missed alerts or improper routing

After Keep:

  • Reduced to only two entry points for alerts
  • Alert logic handled by Keep
  • Only 8 routing rules (down from dozens)
  • Uniform alert payload format
  • Priority/severity standardization
  • Proper team routing based on ownership
  • Critical alerts (P1) automatically route to specific policies with text/phone notifications

"By handling all the logic on the Keep side for priorities, severity, and ownership, we now only need to define where we want to put alerts in our escalation policies. Everything else is handled directly by Keep," says Marco.

Working with Keep: "My Favorite Open Source Project"

JustTrack's experience working with Keep and its team has been overwhelmingly positive.

"From my perspective, and I work with some other open source projects, Keep is currently my favorite open source project," Marco shares. "The responsive team and the joyful growth make it stand out."

Having used Keep for over a year, Marco appreciates the rapid pace of development. "I'm having a hard time staying on top of the version updates, which is a good thing! And the team handles contributions very well, making it a positive experience."

Looking Ahead: JustTrack's Future with Keep

JustTrack sees Keep becoming increasingly central to their observability and alert management strategy:

  1. More Logic and Automation: Expanding their use of Keep workflows, including LLM integration for automated first-response messages
  2. Platform Independence: Reducing dependencies on other alerting platforms as Keep takes on more functionality
  3. Incident Management: Using deduplication and correlations to work with incidents instead of individual alerts, while maintaining complete visibility of all alert information

"The goal is to reduce noise but still not lose any kind of information, have a timeline, and utilize the incident deduplication or correlations in a way that actually works," explains Marco.

Conclusion

Keep has transformed how JustTrack manages alerts across their complex infrastructure, providing the uniformity and consistency they needed while reducing maintenance overhead. The partnership has been characterized by responsive support and continuous improvement, making Keep a critical component of JustTrack's technical stack.

"What I don't like is that you need more and more software-as-a-service products for all your needs," concludes Marco. "That's a strong point for Keep with its advanced functionality—the more extensive the features get, the better it is for the end user to adjust, do custom things, and build upon it."

More content