FR: AI Server Health Check

[Chillout 142]

I’m not sure how common this is, but I recently experimented with using AI to review Emby logs. All I had to do was attach the log file and ask it to look for issues. It was able to quickly summarize and highlight anything that appeared potentially problematic.

FR: It would be great to see something similar built into Emby. An AI-powered server health feature that regularly analyzes logs and provides automated health checks could help users identify issues before they become noticeable problems and advise users when they should seek help on the support forums.

Example output of copilot of server log: 

Overall Assessment

Server health: Good
Database issues: None detected
Transcoding failures: None detected
Playback errors: None detected
Startup-related 503 errors: Present but expected during initialization
Direct Play incompatibility causing transcoding: Present  

Based on this log, I do not see evidence of stream drops, ffmpeg failures, database corruption, tuner failures, or network-related playback errors. The two items worth investigating further are the repeated DirectPlayError conditions and whether they correlate with the playback issues you've observed. 

If you'd like, I can also search the full log specifically for DirectPlayError, seek errors, ffmpeg failures, Live TV tuner issues, or stream termination events to pinpoint any hidden playback problems.

[mwongjay 105]

I think a plugin or an external script that wraps a harness would be more suitable. Adding native integration would be more code and development effort necessary to maintain it in a quickly evolving ecosystem.

[njmckenzie96 7]

Could be a plugin that could point to googles (or similar) ai api. Pretty powerful, even the free tier for users. And reading logs wouldn’t use hardly any tokens, let alone max out the daily free limit. Pointing to the api would then put the ai api keys on the user side and not have to be maintained by the plugin creator or Emby team. That’s basically what I’ve been trying to work on. I just haven’t made an official plugin yet. But it’s in the works. 

[Suliamu 57]

I can understand the -1 very well because this does not belong into emby itself. 
You do it in your monitoring/logging-setup. 
For example Victoriametrics and Victorialogs. 
And you can send not only emby logs there but anything else, make nice notifications and so on. 
In the Unix-World there exists a specific philosophy to write software that serves a specific task and then be good at it. 
Not to create the "superprogram" that basically does it all. 

[Neminem 1987]

TBH If this was ever forced on my server, I would stop using Emby.

I don't want AI to touch anyting I selfhost in any way.

I see the benefits, but I just don't want it, touching anything private.