Skip to main content

Nobl9 release channels

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

We've introduced release channels to enhance the performance and stability of data source integrations. Nobl9 currently has two release channels available:

  1. The Stable channel:
    The Stable channel is a distribution channel that provides all officially released features and changes that have undergone rigorous testing. The stable channel represents the final fully stable product ready for mission-critical production use.
  2. The Beta channel:
    The Beta channel is a distribution channel that showcases the latest innovations and newest functionality, tested to deliver the best early-access experience possible. The beta channel allows users to try out recently shipped features that still need more testing in real-world scenarios. They aren’t considered fully stable yet for production use cases.
caution

Features available in the Beta channel constantly change as the development and testing processes move forward.

What's in the Beta channel?​

Some Nobl9 features have a Beta label, although they aren’t limited to the Beta channel. The difference between these concepts is as follows:

The Beta channel is a way to distribute new functionality
❏ New data sources and new functionality related to the data sources are released to the Beta channel first.
❏ After thorough testing, they go to Stable.
The Beta label shows feature completeness
❏ These features can be available either in Beta or Stable channel
❏ They are released for use as a playground
❏ Nobl9 polishes these features based on user feedback and removes the label once a feature is mature

The following table presents the functionality available in the Beta channel along with the applicable information.

Data sourceAgent min versionBeta functionality
Azure Monitorβ‰₯ 0.69.0-beta04Data source availability
Azure Monitorβ‰₯ 0.71.0-betaResource and metrics discovery
Amazon CloudWatch
AppDynamics
Azure Monitor
Datadog
Dynatrace
Google BigQuery
Elasticsearch
Google Cloud Monitoring
New Relic
Prometheus
ServiceNow Cloud Observability
Splunk
β‰₯ 0.74.0-betaThe N9_DIAGNOSTIC_QUERY_LOG_SAMPLE_INTERVAL_MINUTES variable to modify the frequency of diagnostic logs emission for live SLI ingestion.
LogicMonitorβ‰₯ 0.76.0-beta
  • Agent support
  • Direct support
  • Threshold metrics
  • Ratio metrics

LogicMonitor is currently accessible through sloctl only
beta key takeaways

Currently, Beta is the default channel for all new Nobl9 users.

Switching between release channels​

You can switch between channels using Nobl9 UI or sloctl.

Selecting release channels in UI​

You can choose the release channel for your data source (both Agent and Direct connection method) in the Data source wizard. To do this, navigate to Integrations > Sources, choose your source and connection method (Agent/Direct) and select the release channel from the list menu.

Image 1: Steps to get started with Nobl9
tip

For the agent connection method, remember to deploy your agent in Docker or Kubernetes once you clicked Add Data Source.

caution

You can edit the Release Channel field only for the direct connection method. For agents, this field is inactive in the Edit Data Source step.

Defining release channel in sloctl​

You can define the release channel in sloctl with the sloctl apply command for Agents or Directs. YAML definitions for Agents and Directs include the releaseChannel field that can take one of two values: stable or beta.

Below is an example YAML configuration for an Agent:

- apiVersion: n9/v1alpha
kind: Agent
metadata:
displayName: Agent DT
name: agent-dt
project: default
spec:
dynatrace:
url: https://{}
queryDelay:
minimumAgentVersion: 0.65.0-beta09
unit: Minute
value: 2
releaseChannel: beta
sourceOf:
- Metrics
tip

Check YAML Guide and Sources documentation for more details on YAML definitions for specific Sources and connection methods.

Assumptions​

  • When you edit an existing Agent, you cannot change the value for the releaseChannel field; sloctl will return an error.

  • When adding a new Direct or Agent without specifying the releaseChannel, the default release channel is set to beta.

  • Features labeled as Beta can be available in both channels.

  • For Agents, the releaseChannel field in the Nobl9 database is automatically updated, depending on the Agent version. So when you run the beta agent in your cluster, Nobl9 updates the releaseChannel field in the database to beta automatically.

For a more in-depth look, consult additional resources: