Hey guys, is there any reason why a particular run...
# ask-metaflow
a
Hey guys, is there any reason why a particular run-id does not show up on metaflow UI? I see the following logs, This run-id is a resumed argo-workflow.
Copy code
Metaflow 2.15.14 executing flowTrain for user:j.kollipara
Validating your flow...                                                                                                                                                     
The graph looks good!│
Running pylint...                                                                                                                                                           
Pylint is happy! 
Workflow starting (run-id 1749756923772615):
command i ran is
Copy code
bash -c python flow.py resume --origin-run-id argo-xxxx-yyyy --with kubernetes
d
that is a local run
(sorry, I mean it uses a local metadata service)
so it won’t show up in the ui
did you configure the metadata service and set it up to be used by your flow?
(you can do that either though the CL or through a config file)
a
Yeah, i run this command on a k8s pod. Are you referring to configuring envars ? like
METAFLOW_SERVICE_URL
etc ?
d
yep.
a
hmmm..i do have it as an envar mounted on the pod.
since its resume, it indeed was able to communicate with the metaflow service.
Copy code
- name: METAFLOW_SERVICE_URL                                                                                                                                                                                      
  value: <http://metaflow-metaflow-service.metaflow:8080/>                                                                                                                                                          
- name: METAFLOW_DEFAULT_DATASTORE                                                                                                                                                                                         value: s3                                                                                                                                                                                                       - name: METAFLOW_DATASTORE_SYSROOT_S3                                                                                                                                                                             value: <s3://production-eu-metaflow/metaflow>
d
you might need something liek
METAFLOW_DEFAULT_METADATA
set to
service
.
a
Great, thanks. I was missing the above envar, it works now.