Observability

Overview

Comprehensive observability of your JFrog Platform is essential for maintaining optimal performance, reliability, and security. While this can be achieved in both self-hosted and SaaS, JFrog SaaS significantly simplifies this critical operational aspect.

JFrog SaaS Observability

When using JFrog SaaS, observability is built-in through the JFrog Platform APIs and UI and also through the MyJFrog portal.

JFrog Observability Features

Key monitoring features

• Platform services status (Self hosted only)
• Storage status and allocation
• SaaS logs streaming (SaaS only)
• Readiness and Liveness probes

See more in the Monitoring and Logging help page.

MyJFrog Portal

Some of the key features of the MyJFrog portal include:

• Real-time service health monitoring
• Resource utilization metrics
• Automated alerts and notifications
• Usage trends and statistics
• Security status and compliance reports
• Audit logs and access control

The MyJFrog portal serves as your centralized observability dashboard, eliminating the need for complex monitoring setup and maintenance.

Self-Hosted Observability Requirements

If running a self-hosted JFrog Platform, you’ll need to implement and manage:

Infrastructure Monitoring

• Kubernetes cluster system and application health
• Node resources (CPU, memory, disk) monitoring
• Network connectivity
• Storage providers
• Database health

Platform Availability

• Readiness and Liveness probes
• System logs configuration
• Log analytics setup

Application Metrics & Integration Tools

To achieve comprehensive observability in a self-hosted JFrog Platform deployments, you’ll need to collect application metrics, integrate monitoring tools, and configure alerting and retention policies. Typical observability requirements include:

• Metrics collection (using OpenMetrics format)
• Integration with monitoring tools such as Prometheus and Grafana
• Log aggregation using solutions like Loki, Fluentd or Filebeat
• Alert configuration and automated notifications
• Data visualization and dashboard setup
• Historical data retention and policy management
• Additional monitoring services as needed

A popular example combines Prometheus for metrics collection, Loki for log aggregation, and Grafana for dashboards—in Kubernetes deployments, see the log-analytics-prometheus example for a ready-to-use setup.

Best Practices

JFrog SaaS

• Regularly review MyJFrog dashboards
• Configure notification preferences
• Monitor usage patterns and trends
• Track security compliance

Self-Hosted

• Implement comprehensive monitoring
• Set up proactive alerts
• Configure log aggregation
• Maintain historical metrics
• Define retention policies