Pulse not picking up some tm1 services due to extra spaces in service manifest

We just had a case that had baffeled us for weeks if not months that we had some TM1 instances which were invisible to Pulse even though we could see the services running and connect to them with Arc and Apliqo without issue.

We were able to solve this after troubleshooting with the Code team that the pulse-monitor uses a very strict regex to identify services to monitor and the service manifest files of the tm1 instances which were not picked up by Pulse contained additional spaces in the .service files in /etc/systemd/system.

Documenting this here in case anyone comes accross this issue in the future.

Thanks for sharing this Scott,

The following document was updated as well, you’ll find all the reasons why Pulse will not show a TM1 instance: https://cubewisecare.atlassian.net/wiki/spaces/PIAC/pages/880181249/Reasons+Why+You+Can+t+See+a+TM1+Instance+in+Pulse

Cheers,

Vincent