You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pelican Version: Run ./pelican --version to get version number.
Pelican Service:
Client
Describe the bug A clear and concise description of what the bug is.
Pelican client should attach the project name to user-agent header we requesting objects in the federation. However, currently the user-agent is grab
To Reproduce Steps to reproduce the behavior.
Spin up federation in a box
Put a file under origin exported directory
Request the file using pelican object get
Go to Prometheus metric at /api/v1.0/prometheus/query?query=xrootd_transfer_bytes and watch for the label proj. The entry with path == your origin exported namespace should have corresponding proj="grab"
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. Linux, MacOS]
Browser: [e.g. chrome, safari, if the bug relates to any web user interface]
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Pelican Version:
Run
./pelican --version
to get version number.Pelican Service:
Describe the bug
A clear and concise description of what the bug is.
Pelican client should attach the project name to
user-agent
header we requesting objects in the federation. However, currently theuser-agent
isgrab
To Reproduce
Steps to reproduce the behavior.
pelican object get
/api/v1.0/prometheus/query?query=xrootd_transfer_bytes
and watch for the labelproj
. The entry withpath
== your origin exported namespace should have correspondingproj="grab"
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: