Skip to main content

Coralogix

Reading time: 0 minute(s) (0 words)

The Coralogix and Nobl9 integration leverages Coralogix's Prometheus metrics API to enable SLO management in Nobl9. By utilizing Coralogix's Prometheus-compatible metrics alongside Nobl9's SLOs, teams can effectively monitor application performance and service reliability through PromQL queries. The integration streamlines metrics monitoring workflows, enabling data-driven reliability decisions through Coralogix's metrics capabilities.

Coralogix parameters and supported features in Nobl9
General support:
Release channel: Stable
Connection method: Agent
Replay and SLI Analyzer: Historical data limit 30 days
Event logs: Not supported
Query checker: Not supported
Query parameters retrieval: Supported
Timestamp cache persistence: Supported

Query parameters:
Query interval: 1 min
Query delay: 0 sec
Jitter: 15 sec
Timeout: 30 sec

Agent details and minimum required versions for supported features:
Plugin name: n9prometheus
Query delay environment variable: CORALOGIX_QUERY_DELAY
Replay and SLI Analyzer: 0.65.0
Query parameters retrieval: 0.73.2
Timestamp cache persistence: 0.65.0

Additional notes:
Support for Prometheus metrics API
Learn more Opens in a new tab

Authorization

Agent deployment requires a Coralogix shared team API key. You can create such a key under your Coralogix account's Settings > Keys.

The generated team API key must have the DataQuerying role preset assigned.

Pass the created key as the CORALOGIX_API_KEY value when deploying your Coralogix agent.

Adding Coralogix as a data source

You can add Coralogix using the agent connection method only.

Nobl9 Web

  1. Navigate to Integrations > Sources.
  2. Click .
  3. Click the required Source button.
  4. Choose Agent.
  1. Enter your required Coralogix Domain.
  1. Select a Project.
    Project is a way to organize your Nobl9 resources and manage access to them.
    When Project is skipped, Nobl9 uses the default project.
  2. Enter a Display Name.
    You can enter a user-friendly name with spaces in this field.
  3. Enter a Name.
    The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
  4. You can add Description to your resource, providing extra details about it, its purpose, responsible persons, etc.
    Up to 1050 characters.
  5. Specify the Query delay to set a customized delay for queries when pulling the data from the data source.
    • The default value in Coralogix integration for Query delay is 0 seconds.
    Changing the query delay
    Changing the query delay can affect your SLI data.
    Learn more about query delay and its impact.
  6. Enter a Maximum Period for Historical Data Retrieval.
    • This value defines how far back in the past your data will be retrieved when replaying your SLO based on this data source.
    • The maximum period value depends on the data source.
      Find the maximum value for your data source.
    • A greater period can extend the loading time when creating an SLO.
      • The value must be a positive integer.
  7. Enter a Default Period for Historical Data Retrieval.
    • It is used by SLOs connected to this data source.
    • The value must be a positive integer or 0.
    • By default, this value is set to 0. When you set it to >0, you will create SLOs with Replay.
  8. Click Add Data Source.

sloctl

YAML definition for the agent connection method
apiVersion: n9/v1alpha
kind: Agent
metadata:
name: coralogix
displayName: Coralogix Agent
project: default
annotations:
area: latency
env: prod
region: us
team: sales
spec:
description: Example Coralogix Agent
releaseChannel: stable
coralogix:
domain: coralogix.com
historicalDataRetrieval:
maxDuration:
value: 30
unit: Day
defaultDuration:
value: 15
unit: Day
queryDelay:
value: 1
unit: Second
FieldTypeDescription
queryDelay.unit
mandatory
enumSpecifies the unit for the query delay. Possible values: Second | Minute.
• Check query delay documentation for default unit of query delay for each source.
queryDelay.value
mandatory
numericSpecifies the value for the query delay.
• Must be a number less than 1440 minutes (24 hours).
• Check query delay documentation for default unit of query delay for each source.
releaseChannel
mandatory
enumSpecifies the release channel. Accepted values: beta | stable.
Source-specific fields
coralogix.domain
mandatory
stringA Coralogix domain you need to collect data from.
Replay-related fields
historicalDataRetrieval
optional
n/aOptional structure related to configuration related to Replay.
❗ Use only with supported sources.
• If omitted, Nobl9 uses the default values of value: 0 and unit: Day for maxDuration and defaultDuration.
maxDuration.value
optional
numericSpecifies the maximum duration for historical data retrieval. Must be integer ≥ 0. See Replay documentation for values of max duration per data source.
maxDuration.unit
optional
enumSpecifies the unit for the maximum duration of historical data retrieval. Accepted values: Minute | Hour | Day.
defaultDuration.value
optional
numericSpecifies the default duration for historical data retrieval. Must be integer ≥ 0 and maxDuration.
defaultDuration.unit
optional
enumSpecifies the unit for the default duration of historical data retrieval. Accepted values: Minute | Hour | Day.
  1. Apply your YAML definition using the sloctl apply command.
  2. Deploy your agent in a Kubernetes cluster or Docker container.
For a more in-depth look, consult additional resources: