Closed sosedoff closed 1 year ago
I think @xfalcox noticed a similar issue, in the original versions we supported a bind all and then it was no longer there.
I am happy with this change, but can we update the documentation as well?
Yep, i will update the docs
Yes, had the same problem when updating from .5 to the latest version of this gem in Discourse.
Over there I fixed this problem by passing *
as the bind address, which in glibc means that we will bind to both IPv4 and IPv6. However that doesn't work if someone is using musl. So 👍 for this approach from me.
Should be ready to go!
[arrives late] Hey friends, any plans to release an updated version with this included? I was confused as to why it wasn't working only to release it's not in the 2.0.6 version that is most recent at this time. 😸
will try to post a new version tomorrow!
On Thu, Jan 12, 2023 at 4:20 AM Cory G Watson @.***> wrote:
arrives late Hey friends, any plans to release an updated version with this included? I was confused as to why it wasn't working only to release it's not in the 2.0.6 version that is most recent at this time. 😸
— Reply to this email directly, view it on GitHub https://github.com/discourse/prometheus_exporter/pull/260#issuecomment-1379218995, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAABIXNCV5LOXQBXT2JMYFTWR3TUXANCNFSM6AAAAAATJ6GVHM . You are receiving this because you modified the open/close state.Message ID: @.***>
Appreciated! I just set to pull from head, but lost some time to being confused why the -b ANY
wasn't working for me, only to realize it wasn't released yet. 😆
Starting
prometheus_exporter -v -b ALL -p 8080
will include the log message:netstat: