Sensu-backend connecting out to

Description of your problem

On a fresh install of sensu-backend, I see a TCP connection from sensu-backend out to an external IP address

root@sensu-backend:/home/ubuntu# lsof -i -n -P | grep sensu
sensu-bac 5529           sensu    7u  IPv4  53006      0t0  TCP (LISTEN)
sensu-bac 5529           sensu    8u  IPv4  53007      0t0  TCP (LISTEN)
sensu-bac 5529           sensu   12u  IPv4  53022      0t0  TCP> (ESTABLISHED)
sensu-bac 5529           sensu   14u  IPv4  53023      0t0  TCP> (ESTABLISHED)
sensu-bac 5529           sensu   15u  IPv4  53025      0t0  TCP> (ESTABLISHED)
sensu-bac 5529           sensu   16u  IPv4  53026      0t0  TCP> (ESTABLISHED)
sensu-bac 5529           sensu   18u  IPv6  53051      0t0  TCP *:8080 (LISTEN)
sensu-bac 5529           sensu   19u  IPv6  53053      0t0  TCP *:8081 (LISTEN)
sensu-bac 5529           sensu   20u  IPv6  53055      0t0  TCP *:3000 (LISTEN)
sensu-bac 5529           sensu   22u  IPv4  54433      0t0  TCP> (ESTABLISHED)

The last connection to looks suspicious, a reverse DNS lookup gives

I searched the sensugo docs and googled it as best I could but couldn’t find anything, I looked in the logs - couldn’t see anything there.

Should I be worried? Is this normal? Can I stop it?

Environmental information

Operating system information

<!--Please select the operating system that you're using Sensu Go on-->

Ubuntu 22.04

Package versions

<!--Please provide the package versions for all installed Sensu Go, Etcd, and PostgreSQL packages-->

Sensu Go: 6.9.1+ee

Plugin information

<!--If you're having an issue with a plugin, please use the following section to provide additional details-->

No plugins installed

Hey @madhatter22 :wave:

Your Sensu backend is connecting to Tessen, which is documented here:

Tessen is the Sensu call-home service. It is enabled by default on Sensu backends. Tessen sends anonymized data about Sensu instances to Sensu Inc., including the version, cluster size, number of events processed, and number of resources created (like checks and handlers). We rely on Tessen data to understand how Sensu is being used and make informed decisions about product improvements.

This can be disabled as noted in the docs, but does provide good, anonymized, information for future product improvements



Hi Justin,

Thanks, that makes sense - I couldn’t find it in the docs when I searched but glad to know its expected behaviour.


1 Like

Hey Grant,

Glad to help. Also want to let you know, based on this conversation, I’ve requested an update to the docs to try and bring a bit more light to the dark where Tessen is concerned.