Service Profile not monitoring?

[oceaneLonneux]

Hello, I have a couple of questions regarding service profile :)
1. We tried using the command ‘linkerd routes svc/name-api-svc -t 20s -n=namespace’ but the time is never respected. The command returns the route almost right away. Is that on purpose…? I saw time in the Linkerd route —help, so confused as to why it reacts like that
2. I have been following Linkerd guide for SP (and Digital Ocean https://www.digitalocean.com/community/tutorials/how-to-install-and-use-linkerd-with-kubernetes#step-2-—-installing-linkerd), however we aren’t really getting anywhere.
Here is our yaml, which we applied. The pods are meshed. We use EKS. version 1.15. I checked the service name and it is the correct one.

apiVersion: linkerd.io/v1alpha2
kind: ServiceProfile
metadata:
  name: name-api-svc.namespace.svc.cluster.local
  namespace: namespace
spec:
  routes:
  - name: ‘/name’
    isRetryable: true # Define it's safe to retry this route
    timeout: 100ms # Define a timeout for this route
    condition:
      method: GET
      pathRegex: /name

Is there something we are missing?

Thanks

[adleong]

Hi @oceaneLonneux!

1. The linkerd routes command gets its data from Prometheus and the -t flag controls the time window that it queries. In other words, using -t 20s will return immediately but will show stats that represent the past 20 seconds of data.

2. That service profile looks valid to me. Can you be a bit more specific about what is not working? Are you seeing requests that you expect to be classified under that route getting classified differently? Here are some helpful tips for troubleshooting route issues: https://linkerd.io/2/tasks/getting-per-route-metrics/#troubleshooting

[oceaneLonneux]

Thanks for answering @adleong ! I apologise for the first one, I surely didn't read through enough.

Regarding the second one, we are missing "rt_route" when I look at tap (like mentioned in the guide). I have done a regex ( /(^\w+) ), which I checked on the website provided and seems correct for the path (which is /name). However, I'm afraid it still doesn't get picked up...
We do get the correct authority (the name of our website), src_res, src_ns, dst_res and dst_ns.

[adleong]

I don't think the regex /(^\w+) matches the path /name (the ^ anchor matches the start of the line but you have it after the slash).