Coralogix is deprecating the legacy endpoint previously used for agent log forwarding. To ensure uninterrupted log ingestion for Coralogix agents, some customers may need to update their outbound firewall rules to include the new URL.
Please add the following URL to your firewall allowlist:
For the US data center: https://ingress.us1.coralogix.com/logs/v1/singles
For the EU data center: https://ingress.eu2.coralogix.com/logs/v1/singles
This document explains who is affected, what needs to be updated, how outbound rules work, and what happens if no action is taken.
Who does this apply to?
Only the following customers need to take action.
You must update your outbound rules if BOTH of these conditions are true:
1. You have outbound firewall rules configured (i.e., egress filtering is enabled), and
2. You previously whitelisted the old Coralogix agent logs endpoint.
If this applies to your environment, please ensure that the new Coralogix agent logs URL is added to your allowlist.
You can safely ignore this message if:
You do not have any outbound (egress) restrictions in place, OR
You have never manually whitelisted the old Coralogix agent logs URL.
In these cases, your system will continue working normally.
What Are Outbound Rules?
Outbound rules are firewall or network security controls that restrict which external services your environment is allowed to communicate with. They are commonly used to:
Improve security by limiting external traffic
Enforce compliance requirements
Prevent applications from sending data to unauthorized destinations
How to update outbound rules
If your environment uses outbound filtering, you will typically need to:
Locate the firewall, proxy, or egress control tool used in your environment
(e.g., AWS Security Groups / NACLs, Azure NSGs, GCP VPC Firewall, corporate proxy, on-prem firewall).Find the existing allowlist entry for the old Coralogix agent log URL.
Add the new Coralogix agent logs URL to your allowlist.
Ensure the rule allows:
HTTPS traffic (TCP port 443)
From the Coralogix agent source host(s)
To the new endpoint
Save/apply the updated rules.
Why do you need to make this update?
The impact is not critical to your operations, but it is recommended because:
The agent will not be able to forward its internal logs to Coralogix once the old URL is fully deprecated.
This means the SuperOps team won’t be able to see the agent logs needed to debug issues.
Issues related to the agent (connectivity, configuration, errors) will be much harder to troubleshoot without agent logs.
Future debugging may require firewall changes to resolve potential issues.
📝 Note: This update does not apply to our partners on the Standard - PSA only subscription.
