Emby Metrics Exporter

[Neminem 1518]

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 182]

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 182]

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 182]

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 1518]

@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:)

[Bagul 182]

1 hour ago, Neminem said:

@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.

Ah, sorry, maybe I was more tired than I thought

 

I've fixed the problem, I can't create a new release now, but I'll take care of it tomorrow.

[Neminem 1518]

@Bagulyet again thanks

[Neminem 1518]

@cochize1You really need to learn to use GitHub.

When you have issues, with 3th party dev's.

Its likely they don't monitor forum messageres.

[Neminem 1518]

@cochize1There is a new update.

You can again use latest docker tag.... bagul/goemby_exporter:latest

@BagulThank you for the fix

 

[Bagul 182]

10 minutes ago, Neminem said:

@cochize1There is a new update.

You can again use latest docker tag.... bagul/goemby_exporter:latest

@BagulThank you for the fix

 

Yes, I've deployed the fix. I'll look into updating the geolocation database.

[cochize1 55]

12 minutes ago, Bagul said:

Yes, I've deployed the fix. I'll look into updating the geolocation database.

Great, I'll be looking into this, thanks again

[jleiss 0]

I understand this is no longer mainted, but question about the capturing of data, is that only able be pulled from the local docker environment, or can it grab stuff from anywhere

[Neminem 1518]

No you should be able to point your prometheus config to pull the exporter data on a different pc / server.

[jleiss 0]

5 minutes ago, Neminem said:

No you should be able to point your prometheus config to pull the exporter data on a different pc / server.

it appears to be working but prometheus cannot pull the data. This is what I am seeing, where 172.17.0.2 is the exporter

 

[Neminem 1518]

Is that on a different pc, if it is then you cant use docker ip range.

Use server/host ip

[Neminem 1518]

This is from a different host where I pull iGPU stats.

[jleiss 0]

1 minute ago, Neminem said:

Is that on a different pc, if it is then you cant use docker ip range.

Use server/host ip

No exporter and prometheus are on the same host, only emby is in a different location. I am querying the docker IP

this is my prometheus job

  - job_name: 'emby-exporter'
    scrape_interval: 15s
    static_configs:
      - targets: ['172.17.0.2:9210']
 

[Neminem 1518]

Try with host ip

[Neminem 1518]

What's the output in your exporter logs ?

[jleiss 0]

I get target refused when using the machine IP

exporter logs

jleiss@bree:/opt/prometheus$ docker logs emby_exporter
10:46:36 | INFO  | main.go:37 > Using America/Chicago
10:46:36 | INFO  | app.go:56 > Beginning to serve on port 9210
10:46:36 | INFO  | app.go:57 > You can see the metrics on http://localhost:9210/metrics
11:08:00 | INFO  | main.go:37 > Using America/Chicago
11:08:00 | INFO  | app.go:56 > Beginning to serve on port 9210
11:08:00 | INFO  | app.go:57 > You can see the metrics on http://localhost:9210/metrics
11:15:02 | INFO  | main.go:37 > Using America/Chicago
11:15:02 | INFO  | app.go:56 > Beginning to serve on port 9210
11:15:02 | INFO  | app.go:57 > You can see the metrics on http://localhost:9210/metrics