Influxdb notifications not using the specified http port

[rosswakelin]

Version

2.4.190

Installation Method

Security Onion ISO image

Description

configuration

Installation Type

Distributed

Location

on-prem with Internet access

Hardware Specs

Exceeds minimum requirements

CPU

4

RAM

32

Storage for /

100

Storage for /nsm

1000

Network Traffic Collection

span port

Network Traffic Speeds

1Gbps to 10Gbps

Status

Yes, all services on all nodes are running OK

Salt Status

No, there are no failures

Logs

No, there are no additional clues

Detail

Afternoon.
We have a distributed grid, and are trying to turn on the alerting for things like monitor traffic volume, /nsm filling up etc. We are not running the pro version.
We have configured a notification endpoint etc. and we see that influxdb is trying to send the HTTP POST notifications to our automation server (n8n), but it is sending it to the wrong port. Our server is listening on port 81, but influxdb is sending the post to port 80, despite us hardcoding the URL with the correct port e.g. http://n8n.x.y.z:81/webhook/......
According to the influxdb documentation, we are doing the right thing - does the SO influxdb configuration have anything in it that would rewrite the destination port for this connection??
We have elastalert configured on the same manager box, and it is successfully alerting using the same mechanism (including the requirement for port 81). It looks like it is something influxdb specific.

Thanks in advance
Ross

Guidelines

• I have read the discussion guidelines at Read before posting! #1720 and assert that I have followed the guidelines.

[rosswakelin]

Just to add to the above, we have run tcpdump on the manager, and the connection is definitely going to port 80 on the n8n server, not port 81, and we are seeing the 404 not found error coming back from the server.

[cm-ops]

We just set 8086 for Influxdb, if you are setting your URL in notification endpoints that appears to be the correct way accourding to Influxdb docs.

[rosswakelin]

Sorry, your answer does not make sense to me. We are trying to send FROM influxdb to an endpoint listening on port 81. The outgoing post request from influxdb always tries to go to destination port 80, instead of the port 81 that we have specified in the URL, even though the influxdb docs say that you just have to specify the destination port in the URL.

[cm-ops]

I understand that, more pointing out we only set that port for sending to influxdb, we don't configure any other ports.

It does appear to be something in Influxdb that is setting the default http port to 80, I imagine the default for https is 443 as well. But looking at their documentation it appears your approach to setting the URL is correct based on what I see.

[rosswakelin]

OK thanks, that implies that it is probably an issue with Influxdb then. I just wanted to check that SO wasn't playing with the communications before I went back to Influxdb with the issue.
Thanks for the response.