hi - did you change email alert configuration in 0...
# supportv
Vik
03/15/2025, 1:46 PMhi - did you change email alert configuration in 0.76? in self hosted the environment variables here don't seem to work. I set my port to 587 using these environment variables, but keep getting this error when I hit the test button:
n
Nagesh Bansal
03/15/2025, 2:18 PMHey @Vik , We have a major upgrade in v0.76.0 release.
Let us check on the issue you're facing, meanwhile you can check out migration guide to upgrade to 0.76.0
https://signoz.io/docs/operate/migration/upgrade-0.76
v
Vik
03/15/2025, 3:09 PMthanks @Nagesh Bansal - this is a fresh install - i did check the migration guide too but didn't see anything. I'm thinking because 0.76.0 moved in the alert manager, configuring it may have changed?
v
Vibhu Pandey
03/15/2025, 4:08 PMYes @Vik you're right, here is the new configuration you have to do:
https://signoz.io/docs/alerts-management/notification-channel/email/#configuring-alertmanager
Vibhu Pandey
03/15/2025, 4:08 PMLet us also include this in our migration docs so that it's more discoverable!
v
Vik
03/15/2025, 7:01 PMthanks @Vibhu Pandey, works great 👍
Vik
03/17/2025, 5:22 PMi am facing another issue here with 0.76.0, i was previously sending docker logs to signoz from logspout by configuring a received like: tcplog/docker:
listen_address: 0.0.0.0:2255 and allowing this port in the otel-collector ports in my docker-compose. In the new upgrade the ports configured in otel-collector are not visible on the host. Is there another way to do this now?
Vik
03/17/2025, 5:24 PMi've seen a different approach in your documentation here, but there is also still shows tcplog/docker as a possible receiver:
Copy code
receivers: [otlp, tcplog/docker, httplogreceiver/json]Vik
03/17/2025, 5:29 PMit does seem to start though:
Vik
03/17/2025, 5:29 PM{"log":"{\"level\":\"info\",\"ts\":1742231944.5546074,\"caller\":\"adapter/receiver.go:47\",\"msg\":\"Starting stanza receiver\",\"kind\":\"receiver\",\"name\":\"tcplog/docker\",\"data_type\":\"logs\"}\n","stream":"stderr","time":"2025-03-17T171904.556761532Z"}
n
Nagesh Bansal
03/18/2025, 6:09 AMHey @Vik, PTAL: https://signoz.io/docs/userguide/collect_docker_logs/
v
Vik
03/18/2025, 8:11 AM@Nagesh Bansal that's how i have configured logs already but it seems like something in 0.76.0 is different. None of the ports configured in otel-connector are visible on the host.
otel-collector:
!!merge <<: *db-depend
image: signoz/signoz-otel-collector:${OTELCOL_TAG:-0.111.30}
container_name: signoz-otel-collector
command:
- --config=/etc/otel-collector-config.yaml
- --manager-config=/etc/manager-config.yaml
- --copy-path=/var/tmp/collector-config.yaml
- --feature-gates=-pkg.translator.prometheus.NormalizeName
volumes:
- ./otel-collector-config.yaml:/etc/otel-collector-config.yaml
- ../common/signoz/otel-collector-opamp-config.yaml:/etc/manager-config.yaml
environment:
- OTEL_RESOURCE_ATTRIBUTES=host.name=signoz-host,os.type=linux
- LOW_CARDINAL_EXCEPTION_GROUPING=false
ports:
# - "1777:1777" # pprof extension
- "4317:4317" # OTLP gRPC receiver
- "4318:4318" # OTLP HTTP receiver
- "2255:2255" #OTLP Docker log receiver
Vik
03/20/2025, 10:24 AMcan anyone confirm if someone has changed with regards to the ports that are accessible from otel-collector in the new version? it seems like none of the ports are mapped anymore.
5 Views