Hello,
I created custom metric and attached to one of the components. Then generated API token on account and tried to push some value there:
$ curl --request POST \ --url https://org.atlassian.net/gateway/api/compass/v1/metrics \ --user "$USER_EMAIL:$USER_API_KEY" \ --header "Accept: application/json" \ --header "Content-Type: application/json" \ --data "{ \"metricSourceId\": \"ari:cloud:compass:!id!:metric-source/!id!\", \"value\": $METRIC_VALUE, \"timestamp\": \"$(date -u +'%Y-%m-%dT%H:%M:%SZ')\" }"
But getting:
{"timestamp":"2025-02-09T21:28:15.096+00:00","status":403,"error":"Forbidden","path":"/external/v1/metrics"}%
Documentation on API endpoint saying that user does not have permissions to push metrics, but have `Product Admin` permissions.
Maybe something with our plan, we use Free at this moment.
Any ideas what could be wrong and what to check?
Thanks everyone in advance!
https://developer.atlassian.com/cloud/compass/components/push-metric-values-using-a-curl-command/
https://developer.atlassian.com/cloud/compass/rest/v2/api-group-metrics/#api-compass-v1-metrics-post
Hi, @Dima Slupytskyi !
You're right that Compass admins have permissions to push metric values to metric sources attached to components, as described in https://support.atlassian.com/compass/docs/how-do-compass-permissions-work/
It is possible to set up more detailed permission policies and restrict who can update metric values in Compass premium, but since you're in the free plan, these configurable restrictions shouldn't apply to your example.
That's making me think there might be some disconnect between the identifiers or credentials used for this case. I'm assuming that you copied from the Compass UI the `curl` command placeholders related to the new metric (in the "copy" icon there) so that you are using your own Compass site domain instead of "org.atlassian.net" in https://org.atlassian.net/gateway/api/compass/v1/metrics also with the prepopulated metric source identifier?
An invalid or expired token could also result in a similar error; you can generate a new token for that specific organization in `/manage-profile/security/api-tokens`
If this doesn't solve your issue and you're comfortable sharing the time of your last attempt and your organization domain, we could try taking a deeper look into the application logs to determine what is happening in this specific case.
Hi @Enrique Serrano Valle ,
Thanks a lot for your response!
Yes, token was generated in https://id.atlassian.com/manage-profile/security/api-tokens and even showing that it was last accessed few minutes ago.
My exact steps with organization domain:
$ export USER_EMAIL="my@email"$ export USER_API_KEY="generated token"$ export METRIC_VALUE="1"# use copy icon for curl request$ curl --request POST \--url https://gridesports.atlassian.net/gateway/api/compass/v1/metrics \--user "$USER_EMAIL:$USER_API_KEY" \--header "Accept: application/json" \--header "Content-Type: application/json" \--data "{\"metricSourceId\": \"ari:cloud:compass:!id!:metric-source/4ea518f3-4199-466e-a36b-e657bb1a9d23/38b24391-a08f-4194-8e10-3fd5f52a4267\",\"value\": $METRIC_VALUE,\"timestamp\": \"$(date -u +'%Y-%m-%dT%H:%M:%SZ')\"}"{"timestamp":"2025-02-10T17:06:15.563+00:00","status":403,"error":"Forbidden","path":"/external/v1/metrics"}
$ export USER_EMAIL="my@email"
$ export USER_API_KEY="generated token"
$ export METRIC_VALUE="1"
# use copy icon for curl request
$ curl --request POST \--url https://gridesports.atlassian.net/gateway/api/compass/v1/metrics \--user "$USER_EMAIL:$USER_API_KEY" \--header "Accept: application/json" \--header "Content-Type: application/json" \--data "{\"metricSourceId\": \"ari:cloud:compass:!id!:metric-source/4ea518f3-4199-466e-a36b-e657bb1a9d23/38b24391-a08f-4194-8e10-3fd5f52a4267\",\"value\": $METRIC_VALUE,\"timestamp\": \"$(date -u +'%Y-%m-%dT%H:%M:%SZ')\"}"
{"timestamp":"2025-02-10T17:06:15.563+00:00","status":403,"error":"Forbidden","path":"/external/v1/metrics"}
^ response with exact timestamp
@Dima Slupytskyi that helps. Just double checking based on the sample payload that you've sent: have you also replaced `!id!` by the cloudId of your site when providing the metric source Id?
I assume the line that you'd provide for that call would be:
\"metricSourceId\": \"ari:cloud:compass:89c28397-c088-47b0-b168-9bef03da7559:metric-source/4ea518f3-4199-466e-a36b-e657bb1a9d23/38b24391-a08f-4194-8e10-3fd5f52a4267\",
Yes, was replaced before posting that comment This is full command that I use without any masking:
$ curl --request POST \--url https://gridesports.atlassian.net/gateway/api/compass/v1/metrics \--user "$USER_EMAIL:$USER_API_KEY" \--header "Accept: application/json" \--header "Content-Type: application/json" \--data "{\"metricSourceId\": \"ari:cloud:compass:89c28397-c088-47b0-b168-9bef03da7559:metric-source/4ea518f3-4199-466e-a36b-e657bb1a9d23/38b24391-a08f-4194-8e10-3fd5f52a4267\",\"value\": $METRIC_VALUE,\"timestamp\": \"$(date -u +'%Y-%m-%dT%H:%M:%SZ')\"}"{"timestamp":"2025-02-10T19:47:09.614+00:00","status":403,"error":"Forbidden","path":"/external/v1/metrics"}
$ curl --request POST \--url https://gridesports.atlassian.net/gateway/api/compass/v1/metrics \--user "$USER_EMAIL:$USER_API_KEY" \--header "Accept: application/json" \--header "Content-Type: application/json" \--data "{\"metricSourceId\": \"ari:cloud:compass:89c28397-c088-47b0-b168-9bef03da7559:metric-source/4ea518f3-4199-466e-a36b-e657bb1a9d23/38b24391-a08f-4194-8e10-3fd5f52a4267\",\"value\": $METRIC_VALUE,\"timestamp\": \"$(date -u +'%Y-%m-%dT%H:%M:%SZ')\"}"
{"timestamp":"2025-02-10T19:47:09.614+00:00","status":403,"error":"Forbidden","path":"/external/v1/metrics"}
Sorry for confusion!
It looks like you're new here. Sign in or register to get started.
