Coralogix is an observability platform. You can use Coralogix to drive insights into values such as:
In order to connect Cortex to your Coralogix instance, you’ll need to add a Coralogix API key under Settings → Coralogix.
Multi-account supportCoralogix has multi account support. Each configuration requires an alias. We use the alias to correlate the instance you want to use with the registrations for various entities. There is also a default configuration used by registrations without an alias listed. You can edit aliases and the default configuration under Settings → Coralogix.
If you do not see the Settings page you're looking for in the sidebar, you likely don't have the proper permissions and need to contact your admin.
By default, Cortex will use the entity name or entity tag (e.g.
my-service) as the "best guess" for the Coralogix alert application name. For example, if your entity name is "My Service" and your entity tag is “my-service”, then the corresponding application name in Coralogix should be “My Service” or "my-service".
If your Coralogix application names don’t cleanly match the Cortex entity identifier, you can override this in the Cortex Catalog Descriptor.
If you need to override the automatic discovery, you can define the following block in your Cortex Catalog Descriptor.
Coralogix alerts can be listed in the Catalog under the
Coralogix section. We support application names in the YAML for pulling Coralogix alerts.
- applicationName: my-app # application name tied to alert
alias: my-alias # alias is optional and only relevant if you have opted into multi account support