>Now I still have to get a path on the Linux I am assuming I would keep this as the IP address of the PLC?
Yes.
Is your Linux hardware and application something commercially supported or open-source (like Node-Red or a well known Python library) or is it wholly home-spun ?
I mention it because sitting next to me is a Raspberry Pi 3B running Node-Red and some simple Python scripts and it's on an isolated network where both the Raspberry Pi and the CompactLogix 1769-L30ERMS2 have their Default Gateways set to 192.168.1.1 (and there's no actual gateway or router installed at that address). It's totally normal IPv4 on a private LAN, and it works fine.
In both Node-Red and Python, the target address I use for the CompactLogix is just the IP address. Both the Node-Red EtherNet/IP node and the pylogix (thanks, Dustin !) library have the option to add "1,0" to the end if I were using a slot-mounted ControlLogix or an older CompactLogix, but I don't use that option because I have a "5370" family CompactLogix that has embedded DLR and can either accept direct IP endpoints or emulate a Logix backplane (1,0).
You're describing your system as being intended for "remote monitoring", and mentioned that you are using MQTT to send data to a broker. So I figure you've either got a gateway or router that gives you access beyond the PLC LAN for the MQTT feature, or you've got a device with more than one network interface.