Supported Partner Integrations
JFrog Product(s) | Partner | Integration/ Deployment Type | JFrog Subscription |
---|---|---|---|
ArtifactoryThese platform deployments will deploy JFrog Artifactory as the entry point of the JFrog Platform. | Amazon AWS | Pro/Enterprise | |
Microsoft Azure | Enterprise | ||
Rancher | Enterprise | ||
Red Hat | Pro/Enterprise | ||
Red Hat OpenShift | Enterprise | ||
Atlassian JIRA | Build Information | ||
ServiceNow | Build Information | ||
PagerDuty | PagerDuty | ||
HashiCorp | Hashicorp Vault Artifactory Secrets Plugin | Pro/Enterprise/Enterprise+ | |
Artifactory and XrayThese platform deployments have the option to install Artifactory and additional products. | Amazon AWS | Pro/Enterprise | |
Google GCP | Enterprise | ||
Microsoft Teams | Microsoft Teams | ||
Salesforce Slack | Slack | ||
Red Hat Ansible | Pro/Enterprise | ||
XrayThese platform deployments will deploy JFrog Xray and will take as input the URL and Join key needed to connect to an existing JFrog Artifactory instance. | Microsoft Azure | ||
Red Hat OpenShift | |||
PagerDuty | PagerDuty | ||
Hashicorp | Hashicorp Terraform Provider for JFrog Xray | Pro/Enterprise/Enterprise+ | |
ServiceNow | ServiceNow Spoke | ||
PipelinesThese platform deployments will deploy JFrog Pipelines and will take as input the URL and Join key needed to connect to an existing JFrog Artifactory instance. | PagerDuty | PagerDuty | |
Dynatrace | Pipelines-Dynatrace Reference Design | ||
Container RegistryThese platform developments will deploy JFrog Container Registry and take as input the URL and Join key needed to connect to an existing JFrog Artifactory instance. | Amazon AWS | ||
Google GCP | |||
Microsoft Azure | |||
Rancher | |||
Observability Integrations | Observability Integrations |
Observability Integrations
The JFrog Platform’s unity is powered by many microservices, each with its own log record. When spread across multiple nodes, as with a high-availability JFrog Platform deployment (JPD), the complete picture of your platform operation may be dispersed across 25 or more logs in your network.
Operations teams need a way to bring this JPD log data together into a single collection, to analyze performance and track down operating problems. Even a small enterprise JPD might record millions of transaction events each day, operators need to be able to connect that data to a powerful analytics tool that can help find insights.
JFrog now offers tools that make the real-time view of the entire platform’s operation much easier, through the analytics and visualization tool you already use. JFrog offers integrations with the following vendors:
Partner Vendor | Self-Managed Licenses |
---|---|
Self-Managed Licenses | |
Self-Managed Licenses | |
Self-Managed Licenses | |
Self-Managed | |
SaaS, Self-Managed |
To enable JFrog to support numerous log vendors, an open source common logging platform Fluentd is used. It covers log input and field extraction for all products in the JFrog Platform and structures them as JSON. As part of the downstream data processing, the JSON output is forwarded leveraging the plugins to the desired log vendors such as Splunk, Datadog, EFK, and Prometheus. To learn more about Fluentd, see the Fluentd documentation. JFrog Platform users who want to use our log analytics will install td-agent for fluentd and configurations per Artifactory node. Fluentd supports HA configuration by shipping logs to a fluentd log aggregator which is configured in a HA setup to prevent the log aggregator service from downtime in the event of a crash of the aggregation node. Below is a link with more details on HA setup for Fluentd. The aggregated data from Fluentd is plugged into different log analytics tools to search, analyze and visualize the data. The tools will start populating the JFrog logs dashboard to present timeline and count data for key operating metrics. Some of the metrics supported in the dashboard areUnified Logging Layer - Fluentd
Configuring Fluentd with the JFrog Platform
Viewing Log Data in JFrog Dashboards