Some massive bundle issues with my Plex Server install highlighted a few missing and desperately needed tools for server administration.
We need a way to view who is (and was) using our servers. Not just "Now Watching" but something with historical information in it as well. Logs that can (and should) go back from install of server, if the admin so wishes. Not just a stream of starting and stopping, but REAL information like user x watched the whole of XYZ video, but only watched half of ABC. (How much was streamed/transcoding.) So I can change the format or resolution of the videos without affecting the user's place in the video.
We need an easy way to reset broken/corrupt bundles on the server. This is such a common thing for me now, I am thinking about setting up a chron job/#bash to do this on a daily basis, just for regular maintenance. Maybe a reset bundles button in the web app, or call in the start-stop.sh?
We need a way to kick users off the server without completely shutting the server down. I don't mean revoking their permissions, but a way to stop an active (or locked up) stream. And with the huge influx of Plex Thieves of late, a way to BAN a user, IP range, etc. (Black list, no need for white list.) This needs to be on the server, and not relying on router mechanics or Plex.tv to implement.
We need a way to get some metrics on the media on the server. How much of a given media container type, encoding, both video and audio, and a way to sort this information to help server admins reduce or eliminate transcoding on devices that can't handle it. (I see something like Transmogrify but with more information available. Separate tabs for movies, TV, Music, etc.) And not only does this provide information on the video, but when you click the pie chart it goes straight to a filtered search of that media across libraries so you can see which are the exact videos involved.
A reliable method WITHIN Plex itself, for notifying the users of the new videos, trending videos, etc. Something they can subscribe to, if they wish, providing email, phone numbers for texting, etc. (Yes I know, PlexNotify, which, sadly can't be run on a vast majority of NAS servers out there.)
Less reliance on Plex.tv for client authentication. Again, last night I had issues getting to the site. So while trying to get things settled into folders, naming, etc. I kept getting unauthorized errors getting into my server from the web interface. The token has been issued once, so why does it need to be redone every time I log in? Once a day/2 days/week should be enough, if I am providing log on information that is consistent and recognized at least one time during the admin's preconfigured time frame.
Parse-able logs within Plex Web itself. We should be able to view the log files within the web app just like on a router, cable modem or other types of servers. Having to navigate to some obscure directory to open these logs is to cumbersome for computer neophytes, and just a pain for some of us old timers.
Configurable backup locations for the media library. If I want to back it up, where does this back up go? As it sits now, I have no idea. ( I'm sure someone will post it later, though.) If I want to store that back up off-site or on a separate external drive, I should be able to set it up and have it go there, when I want it to. (And don't tell me this is a function of the OS. Backing up the library is built in to one of the server settings already, this just extends the functionality to make it truly a back up instead of a band-aid.)
Right now, I added 2 new movies to my collection. Plex is maxing out the CPU on my server, and I have no indications of WHY within the web app itself. Systems monitors are telling me it's Plex and give a PID, but that's it. (I KNOW why it's happening, but I should be able to SEE why it's happening with in the web app itself!) Is it making index files, downloading metadata, posters, etc.
I should be able to tell Plex how much CPU to use for making the index files. Don't take all the CPU to do it, unless that's what I have it set up to do. (This is why the CPU is so high above, but come on, this function doesn't need to take 100% of the CPU when it's running!)
Some of these things have been requested for a LONG TIME! Instead we get additional clients (Plex Pass required.) that have limited functionality compared to other clients. Clients that are broken or missing some of the MAJOR aspects of new server releases. (iOS and Plex Home comes to mind, even though I don't use iOS.)
Stop making new clients with half baked feature sets. Flesh out the SERVER that these clients all need to run. Then add to existing clients. THEN and ONLY then when all the existing clients are up to a common level of functionality, add in new clients. As it is now, so many things aren't working or are completely missing, people are starting to look at alternatives.
