Nobl9 release channels
We've introduced release channels to enhance the performance and stability of data source integrations. Nobl9 currently has two release channels available:
- 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. - 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.
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 following table presents the functionality available in the Beta channel along with the applicable information.
Data source | Agent min version | Beta functionality |
---|---|---|
Azure Monitor | β₯ 0.69.0-beta04 | Data source availability |
Azure Monitor | β₯ 0.71.0-beta | Resource 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-beta | The N9_DIAGNOSTIC_QUERY_LOG_SAMPLE_INTERVAL_MINUTES variable to modify the frequency of diagnostic logs emission for live SLI ingestion. |
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.
For the agent connection method, remember to deploy your agent in Docker or Kubernetes once you clicked Add Data Source.
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
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 tobeta
. -
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 thereleaseChannel
field in the database tobeta
automatically.