Package Reroute Logs for PTC
View, interpret, and use Package Traffic Controller (PTC) reroute log lines in JFrog Artifactory for verification, audit, and troubleshooting.
Package Reroute Logs in Artifactory
When traffic follows PTC, JFrog Artifactory records package reroute events in system logs. These entries help verify that installs were redirected through Artifactory, which registry type was involved, and which source and target URLs were used.
Where to View Them
- In the JFrog Platform UI, open Administration.
- Go to Monitoring → Artifactory Logs (path names can vary slightly by release. The goal is the Artifactory log viewer under administration and monitoring).
- Select
artifactory-service.log(or download it for offline search).
You can pause, refresh, or download the log file depending on UI options. Large files are normal on busy instances.
Example Line for npm
2026-04-28T08:48:37.574Z [jfrt ] [INFO ] [5133f38050b3a8fab28558dbac15d947] [7.0.0.1-8081-exec-13] - Reroute: method=GET user=anonymous registry=npm original=https://registry.npmjs.org/mcp-remote target=https://acme.jfrog.io/artifactory/api/npm/npm-remote-registry/mcp-remote userAgent=npm/11.12.1 node/v25.9.0 darwin arm64 workspaces/falseWhat Each Part Means
| Fragment | Meaning |
|---|---|
| Leading timestamp | Request time in UTC (ISO-8601). |
[jfrt ] / [INFO ] | Artifactory service tag and log level. |
| Bracketed hex id | Trace / correlation identifier for that request (useful when matching to other log lines or support cases). |
Reroute: | Package reroute event line. |
method=GET | HTTP method used for the reroute-related request (most package metadata and tarball flows use GET). |
user=… | Identity associated with the request as Artifactory logs it. Depending on your setup, this may appear as anonymous or a mapped user identity. |
registry=… | Package ecosystem for this reroute (for example npm, pypi, docker—aligned with how Package Reroute is configured). |
original=… | Upstream URL the client intended (the public registry URL before Artifactory’s reroute logic applied—for example https://registry.npmjs.org/...). |
target=… | Artifactory URL the client is sent toward after reroute (your remote npm API path under /artifactory/api/npm/<remote-repo>/...). |
userAgent=… | Package manager and runtime fingerprint (for example npm version, Node version, OS, architecture). Helps reproduce issues and spot outdated or unexpected clients. |
Scoped packages and paths with special characters appear URL-encoded in log lines (for example %2f for / in scoped npm names), which is normal.
Why This Matters for Customers
- Audit and forensics: Prove that a given install attempt flowed through your governed Artifactory path, not only direct-to-registry.
- Triage: Compare
originalvstargetwhen a redirect or repository mapping looks wrong. - Client hygiene: Use
userAgentto identify old npm/pip/Docker clients after policy changes. - Ownership: Correlate
user=anduserAgent=with your identity and endpoint telemetry to troubleshoot client behavior. - Dependency installs: Reroute events cover redirect handling; additional dependency fetches can appear as standard repository traffic.