DM-41591: Include a visit with no template coverage in the upload.py test #108
Conversation
doc/playbook.rst
Outdated
| .. code-block:: sh | ||
| kubectl port-forward svc/kafdrop -n kafka 9000:9000 | ||
| Then messages can be viewed locally via Kafdrop at `http://127.0.0.1:9000/topic/rubin-prompt-processing`_. |
There was a problem hiding this comment.
What does "locally" mean? Do you run these on USDF?
Is this better than using https://usdf-rsp.slac.stanford.edu/kafdrop/topic/lsst.sal.ScriptQueue.logevent_nextVisit?
There was a problem hiding this comment.
This would be one way to check the file arrival notifications from the bucket, not the nextVisit messages. If I understand correctly, they are on separate kafkas (nextVisit from sasquatch's and prompt processing has its own).
I got the tip from this slack thread when we were debugging some ceph setup. I swear it was working at one point, probably from my laptop.
However, it seems no longer working probably because we didn't move the service to phalanx when we transitioned. I'll check with Dan. I'll leave out this part as it isn't really relevant to this ticket anyway.
There was a problem hiding this comment.
My mistake with mixing up the two Kafkas. Unfortunately, the instructions on the Slack thread also don't make it clear which system you're supposed to do what on...
hsinfang
force-pushed
the
tickets/DM-41591
branch
from
beb178c to
c6675a2
Compare
|
Funny thing is I originally had each topic on separate commits and squashed them thinking it was too many. They are now separate again. |
hsinfang
force-pushed
the
tickets/DM-41591
branch
2 times, most recently
from
8cebbbf to
f20c6be
Compare
hsinfang
force-pushed
the
tickets/DM-41591
branch
from
f20c6be to
6f2ff63
Compare
2 participants
No description provided.