Emby Metrics Exporter

[cochize1 55]

That's a bummer. Thanks for the info.

[Bagul 184]

17 hours ago, cochize1 said:

I have noticed sth strange with the exporter output and thought you guys could help @Bagul@Neminem

Sometimes (rather more often now) when exporting emby_sessions metrics to Grafana into the table I get the strange result that when someone is playing a series with Show name and Episode name and there is another row when someone is playing a movie with just a Movie name, the table gets filled with the nearby Show name as well. Don't know how to explain it well but the picture shows what I mean. Any idea how to make it blank where it should stay blank?

 

Hello,

I had identified the problem, it will be solved in a last update.
Just in case for people who detect a problem it would be necessary to open a new issue on GitHub.

[Neminem 1709]

@BagulThank you so much

[Bagul 184]

23 hours ago, cochize1 said:

I have noticed sth strange with the exporter output and thought you guys could help @Bagul@Neminem

Sometimes (rather more often now) when exporting emby_sessions metrics to Grafana into the table I get the strange result that when someone is playing a series with Show name and Episode name and there is another row when someone is playing a movie with just a Movie name, the table gets filled with the nearby Show name as well. Don't know how to explain it well but the picture shows what I mean. Any idea how to make it blank where it should stay blank?

 

I've updated the docker image, let me know if you still encounter the problem (or any other problem)

[Neminem 1709]

Looks good in my test.

@BagulThank you

@cochize1how about you ?

[cochize1 55]

When redeploying the stack in Portainer that had Emby Exporter in it I get this error in the logs:

19:28:35 | INFO  | main.go:37 > Using Europe/Warsaw
19:28:35 | INFO  | logger.go:107 > Server is not reachable
19:29:37 | INFO  | main.go:37 > Using Europe/Warsaw
19:29:37 | INFO  | logger.go:107 > Server is not reachable
19:30:40 | INFO  | main.go:37 > Using Europe/Warsaw
19:30:40 | INFO  | logger.go:107 > Server is not reachable

In the same stack I have some other containers that work just fine after redeploying. What could be the problem as my knowledge is quite limited and all I can do is all hit and miss trial and error guessing?

 

[Neminem 1709]

I don't know portainer.

I use docker pull command to update.

How to Upgrade Docker Containers to Apply Image Updates

Edited January 10, 2025 by Neminem

[cochize1 55]

I should have just waited for watchtower to do it's thing...

I am using simple docker compose now:

services:
    goemby_exporter:
        container_name: emby_exporter
        environment:
            - CONFIG_FILE=/config/config.yml
            - TZ=Europe/Warsaw
        volumes:
            - /volume1/docker/embyexporter/config:/config
        ports:
            - 9210:9210
        image: bagul/goemby_exporter:latest
        restart: always

but it seems that the container cannot access the Emby server although I am using the same config.yml as before and point to the right direction:
 

server:
  url: "https://server.com"
  port: 443
  token: "7c749f2a-changed-53b77f51bd823c463c"
  userID: "f769c6f-changed-619762c4ae4eb1b5c9"
options: 
  geoip: true

I am clueless right now. Any tips how to do it from scratch maybe?

[Neminem 1709]

Please hide you tokens and use id.

Those can be mis used.

Edited January 10, 2025 by Neminem

[Neminem 1709]

Try without setting TZ.

19:28:35 | INFO | main.go:37 > Using Europe/Warsaw

 

[cochize1 55]

did that already, all that changed was: 19:28:35 | INFO | main.go:37 > Using UTC

I changed the tokens to some random srings, no worries

Edited January 10, 2025 by cochize1

[Neminem 1709]

Also in your config, what is this

url: "https://server.com" 

I use 

url: "http://192.168.1.4"
As its a local url.

[Neminem 1709]

and port 8096

[cochize1 55]

Bingo! That was it:)

I have had my ddns path there for remote access. But now when I changed it to local url is is up and running again.

Thank you for the tips.

And as for the update, it also seems to be working:)

[cochize1 55]

I have one more question to @Bagul

Sometimes I notice that the IP does not match location. But when I check the same IP that is shown on i.e. ipinfo.io the location there is correct. I usually notice that when I see that a friend is watching a movie on a TV in his home but the location says he is in some other location. Do you know if that can happen or it's just me?

[Neminem 1709]

Well that is logical.

There are many factors involved in this.

VPN usage, CGnat, cell tower location and more jazz.

And on top of that PC don't have a GPS chip in them that is precise enough.

If the user uses a phone, they might not have enable location.

Or are behind VPN usage, CGnat, cell tower location and more jazz.

But how are the exporter supposed to know that, as it only gets what Emby knows.

And that is a IP address ( behind VPN usage, CGnat, cell tower location and more jazz. )

@cochize1

Edited January 10, 2025 by Neminem

[cochize1 55]

Yeah, I thought about all that as well BUT, checking the same IP on any IP finder site gives a correct location.

And I only check the obvious cases out of curiosity. Say, I see a friend watching a movie at his home on his Samsung TV (95% sure he is not using any VPN or hotspot from his cell) and exporter says he is in other city (but the IP finder sites give correct location). 

[Bagul 184]

1 hour ago, cochize1 said:

When redeploying the stack in Portainer that had Emby Exporter in it I get this error in the logs:

19:28:35 | INFO  | main.go:37 > Using Europe/Warsaw
19:28:35 | INFO  | logger.go:107 > Server is not reachable
19:29:37 | INFO  | main.go:37 > Using Europe/Warsaw
19:29:37 | INFO  | logger.go:107 > Server is not reachable
19:30:40 | INFO  | main.go:37 > Using Europe/Warsaw
19:30:40 | INFO  | logger.go:107 > Server is not reachable

In the same stack I have some other containers that work just fine after redeploying. What could be the problem as my knowledge is quite limited and all I can do is all hit and miss trial and error guessing?

 

I'm sorry, it's my fault. I've created a new version which normally fixes the problem if the server url starts with https.

[Bagul 184]

1 minute ago, cochize1 said:

Yeah, I thought about all that as well BUT, checking the same IP on any IP finder site gives a correct location.

And I only check the obvious cases out of curiosity. Say, I see a friend watching a movie at his home on his Samsung TV (95% sure he is not using any VPN or hotspot from his cell) and exporter says he is in other city (but the IP finder sites give correct location). 

When creating the docker image, I retrieve a database for geolocation so as not to use an external service (for reasons of confidentiality and I don't want the service to stop working one day). Over time, geolocation may diverge from reality, as some operators don't deliver a fixed ip but a dynamic ip.

[cochize1 55]

So basically the data for IP location is fixed and is not being updated overtime? And there is no workaround for that? And also, is it being updated with every new image pull of the exporter?

[Bagul 184]

5 minutes ago, cochize1 said:

So basically the data for IP location is fixed and is not being updated overtime? And there is no workaround for that? And also, is it being updated with every new image pull of the exporter?

Yes, the database is local and is only updated with a new version of the exporter. I'd look into retrieving the information in another way, or updating the database directly in the exporter if you like.

[cochize1 55]

Well, I just found out today that you're not planning on releasing new versions since you don't use Emby anymore BUT please do now that we appreciate what you have done for us so far. So if you could poke around and find a solution for that one last issue (we have noticed) just for the kicks of it I personally would like that very much:)

[cochize1 55]

Any idea why it stopped working again overnight? I keep getting the same error:

11:41:13 | INFO  | logger.go:107 > Server is not reachable

[Neminem 1709]

@cochize1if you use this 

bagul/goemby_exporter:v1.0.11

You are back in business, but with out the fix to tv shows spill over.

@BagulThanks for the update, the fix to https broke http and https.

[cochize1 55]

back in square one for now I guess:)