Emby Analytics

[brothom 177]

I couldn´t find an FR matching this description so here goes.

I would like to see a feature that provides some (basic) analytics for Emby Server. For example, for my server I would like to know which media items are:

• Most viewed (filter by viewed, date from, date to)
• Most Favorited (filter by favorites date from, date to)
• Watched in the last X-days
• etc

The reason for this is to get some insights in what my users actually watch without having to ask them all what they think about a certain piece of media personally. This data could be gathered anonymously, without displaying the actual user data to conform to some sort of privacy laws wherever those are.

[user24 313]

Hey, just wondering if you seen this thread (and possibly other similar ones):

https://emby.media/community/index.php?/topic/87043-tautulli-for-emby/

I'm not suggesting it as a complete workable solution for what you want, but just something you could be interested in. There might be something here with Tautulli/Embystat/Jellystat/etc that gives some ideas or perhaps even something you could adapt or build upon with your tech skills (if you have the time and want to, of course).

There's also a tool here that could be a starting point into further utilizing the Emby API:

https://emby.media/community/index.php?/topic/130184-lightweight-emby-dashboard-for-personal-use/

I haven't tried it myself, so no idea if it could be of any use for you???

Yeah, more analytics (as a core part of Emby) is a good idea... I expect others may be able to offer more suggestions...

[GrimReaper 4739]

1 hour ago, brothom said:

I couldn´t find an FR matching this description so here goes.

I would like to see a feature that provides some (basic) analytics for Emby Server. For example, for my server I would like to know which media items are:

• Most viewed (filter by viewed, date from, date to)
• Most Favorited (filter by favorites date from, date to)
• Watched in the last X-days
• etc

The reason for this is to get some insights in what my users actually watch without having to ask them all what they think about a certain piece of media personally. This data could be gathered anonymously, without displaying the actual user data to conform to some sort of privacy laws wherever those are.

Playback Reporting plugin should cover most of those (and a lot more), both visually and tabularly; it allows for (internal) db queries as well. 

Edited August 28, 2025 by GrimReaper

[brothom 177]

19 minutes ago, user24 said:

https://emby.media/community/index.php?/topic/130184-lightweight-emby-dashboard-for-personal-use/

I haven't tried it myself, so no idea if it could be of any use for you???

5 minutes ago, GrimReaper said:

Playback Reporting plugin should cover most of those (and a lot more), both visually and tabularly; it allows for (internal) db queries as well. 

For both cases I prefer internal implementations in stead of slapping a plugin on every feature I'd like. Not too fond of plugins personally due to how they tend to "abuse" the system. As a developer myself I see my users / customers use too many plugins which causes massive dependencies in the long run and sometimes even holding back updates/upgrades because of those dependencies.

 

21 minutes ago, user24 said:

Yeah, more analytics (as a core part of Emby) is a good idea... I expect others may be able to offer more suggestions...

Yep. I would prefer that as well. it doesn't have to be complicated or even dynamic. It's not like I'd want to run quarterly numbers or anything. Just curious what my users are doing without having to scroll through the Activity log and maybe see which types of media are consistently failing to play or whatever.

[Neminem 1518]

I use a combo og grafana and jellystats

 

CyferShepard/Jellystat: Jellystat is a free and open source Statistics App for Jellyfin

[rbjtech 5284]

The Playback Reporting plugin uses it's own database and simply uses the standard API to gather the info.   It's only dependency is if the core API charges for session details - unlikely.

Even if it did, the Plugin is open source on Github.

Given that not everybody wants stats, I would actually counter and say having this external is a perfect use of a Plugin - remembering many of the available plugins were originally part of the 'Core' but were decoupled (and are now official Plugins) to ease the Core complexity and testing cycles.

Edited August 28, 2025 by rbjtech

[brothom 177]

1 hour ago, Neminem said:

I use a combo og grafana and jellystats

 

CyferShepard/Jellystat: Jellystat is a free and open source Statistics App for Jellyfin

Pretty cool, but doesn't that mean you have to keep both Grafana and Jellystat updated all the time? 

1 hour ago, rbjtech said:

The Playback Reporting plugin uses it's own database and simply uses the standard API to gather the info.   It's only dependency is if the core API charges for session details - unlikely.

Even if it did, the Plugin is open source on Github.

Given that not everybody wants stats, I would actually counter and say having this external is a perfect use of a Plugin - remembering many of the available plugins were originally part of the 'Core' but were decoupled (and are now official Plugins) to ease the Core complexity and testing cycles.

I disagree and also makes my point: it's an entirely separate entity that has to be maintained separately as well.
Not everybody wants stats and they don't háve to use it if it's optional? I'd envision it like debug mode which is off by default.

On another note; I can't really imagine that a couple of aggregate tables take up a lot of resources serverside. That would be bad design. Regardless; I agree, it should still be optional.

Edited August 28, 2025 by brothom

[rbjtech 5284]

Lets agree to disagree. 

In the 2 years this extremly popular plugin has been available - it has only had one Compatibility Update - all the other changes have been enhancements.

If a Plugin uses the standard Emby Plugin framework and is coded to good standards, then it simply shouldn't need frequent updating as the who point of an API and associated Emby libraries / NuGet packages is to remove the need for this.

Anyway - it's an excellent Plugin - I highly doubt any internal stats would have a desire to match what this Plugin can do - tbh, I'm surprised it's not installed out the box.

[Neminem 1518]

10 hours ago, brothom said:

Pretty cool, but doesn't that mean you have to keep both Grafana and Jellystat updated all the time? 

Sure it does, and why would I not ?

[brothom 177]

16 hours ago, rbjtech said:

Lets agree to disagree. 

Anyway - it's an excellent Plugin - I highly doubt any internal stats would have a desire to match what this Plugin can do - tbh, I'm surprised it's not installed out the box.

I'm sure it is, but it's besides the point of my FR. I'm not here to talk down this plugin by any means, but I'd prefer an integrated functonality to cover this.

 

6 hours ago, Neminem said:

Sure it does, and why would I not ?

It's a nice alternative but I'm a really lazy dude and prefer to put my energy into managing my library and discovering new content rather than hooking in new services.

I have way too many hobbies as it already is and an integrated implementation would tickle my fancy because of the aforementioned reasons.