I have what I thinks is a standar layout of a Phoenix project, in my lib folder I have two projects app_core and app_interface. In app_interface I have the dependency to phoenix and following this post I also have the dependency to {:prometheus_ex, "~> 1.0"}, {:prometheus_plugs, "~> 1.0"} Given th…

[image] favetelinguis: So lets say in my lib folder I have 5 projects that all depend on each other Do you mean 5 apps in an umbrella setup? If you don’t have an umbrella setup and just one elixir app, there is nothing special to do. If you have an umbrella setup with different apps, I woul…

Prometheus is an external tool, so you send events/metrics to prometheus. You can send metrics from different apps/projects, your metrics endpoint could retrieve data from prometheus to show it to a user? I think prometheus already has a UI/works with grafana so it might be better to just use those? …

I am using the prometheus package without a phoenix installation. The package lets you define, set, update and delete metrics. It’s useful to look at the docs for the specific metrics types to see how you can use them. E.g. prometheus.ex/lib/prometheus/metric/gauge.ex at master · prometheus-erl/pr…

Not sure we have the same view of Prometheus, you dont send data. Prometheus is polling the metrics endpoint wich contains data from instrumented parts of your app.

Maybe I don’t understand correctly how Prometheus works, but I got from this overview you can send your metrics to a push gateway from which prometheus will pull info? If so, that might make it easier to use? Otherwise you’d have to gather the metrics yourself, store/remember them before prometheus …

[image] Tuxified: Maybe I don’t understand correctly how Prometheus works, but I got from this overview you can send your metrics to a push gateway from which prometheus will pull info? That is only meant for things like queue workers where you want to send metrics of individual jobs. [im…

I came across a project that might function as an example: GitHub - oestrich/ex_venture: Text based MMORPG engine written in Elixir · GitHub → Exventure - . Hope that helps :slight_smile:

Ok interesting, my understanding was that prometheus.ex is only used for instrumenting your code, it does not provide an exporter, that is the metrics endpoint will not be provided by it. For that you have to use som other package that provides the endpoint? Do you have any github projects where yo…

The package provides everything you need. So, given you use it in your code to declare and update metrics like this: Prometheus.Metric.Boolean.declare([name: :my_metric, help: "My Metric", labels: [:label1, :label2], registry: :all]) Prometheus.Metric.Boolean.set([name: :my_metric, labels: ["foo",…

So lets say in my lib folder I have 5 projects that all depend on each other, would I need to provide 5 /metrics endpoints on 5 web servers on 5 different ports or could I use one metrics endpoints for all 5 projects? This is sort of my original question.

Just thinking, prometheus_ex uses ETS to store the metrics, so you might not even need an additional metrics app in an umbrella setup. I can’t say for sure but if all apps in the umbrella setup use the prometheus_ex package directly, they should all use the same ETS tables and therefore have a share…

Instrumenting my business logic with Prometheus

Questions & Help Questions

Phillipp July 12, 2018, 10:29am 6

That is only meant for things like queue workers where you want to send metrics of individual jobs.

That is what the prometheus_ex lib does.