# \#logs

**URL:** https://community.tulip.co/tag/logs/377.md

[Latest](https://community.tulip.co/latest.md) · [Categories](https://community.tulip.co/categories.md) · [Tags](https://community.tulip.co/tags.md)

---

## [Log OPCH start and stop](https://community.tulip.co/t/log-opch-start-and-stop/14650)

<div class="topic-metadata">

**Author:** [@fti](https://community.tulip.co/u/fti)\
**Replies:** 1\
**Last updated:** [May 8, 2025, 1:07pm UTC](https://community.tulip.co/t/log-opch-start-and-stop/14650 "2025-05-08T13:07:10Z")

</div>

Greetings. I’ve had several cases where I had issues with an OPCH on a customer’s network which lead me to inspect the Docker container’s logs. I know OPCH logs are probably not the most used “feature” in Tulip, but in …

---

## [On-Premise Connector Host (OPCH) and logs](https://community.tulip.co/t/on-premise-connector-host-opch-and-logs/13446)

<div class="topic-metadata">

**Author:** [@mellerbeck](https://community.tulip.co/u/mellerbeck)\
**Replies:** 2\
**Last updated:** [January 6, 2025, 3:35pm UTC](https://community.tulip.co/t/on-premise-connector-host-opch-and-logs/13446 "2025-01-06T15:35:26Z")

</div>

When troubleshooting OPCH issues Tulip Support asks for the logs (makes sense) I wouldn’t be opposed to streaming the logs to tulip using syslog or anything.