Nobl9 release channels
We've introduced release channels to enhance the performance and stability of data source integrations:
The Stable channel is mature and most reliable. It 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. When you don't need the newest features, the Stable channel would be optimal for use.
The Beta channel showcases the latest innovations tested to deliver the best early-access experience possible. It contains the most recently shipped features that still need more green runs in real-world scenarios, such as usability testing. The Beta channel constantly receives updates and fixes as the development process moves forward. All new features are first delivered to the Beta channel.
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 distribution method:
- New data sources and related functionality are released to the Beta channel first
- After thorough testing, they go to the Stable channel
- The Beta feature label indicates feature completeness
- These features 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 contains the functionality available in the Beta channel along with the applicable information.
Data source | Agent min version | Beta functionality |
---|---|---|
ThousandEyes | β₯ 0.93.0-beta | Support for API v7 |
LogicMonitor | β₯ 0.81.0-beta | sloctl |
Azure Monitor managed service for Prometheus | β₯ 0.78.0-beta | sloctl |
Azure Monitor | β₯ 0.71.0-beta | Resource and metrics discovery |
Azure Monitor | β₯ 0.69.0-beta04 | Data source availability |
- Beta features can be available in both channels.
- You can modify your data source's release channel only if it's connected with the direct method.
Release channel in a YAML definitionβ
The release channel is specified in the releaseChannel
field of your agent or direct YAML:
apiVersion: n9/v1alpha
kind: Agent
metadata:
name: generic
displayName: Generic Agent
project: default
annotations:
area: latency
env: prod
region: us
team: sales
spec:
description: Example Generic Agent
releaseChannel: stable
generic: {}
queryDelay:
value: 1
unit: Second
Provide the required release channelβstable
or beta
βand run sloctl apply -f
providing the path to your YAML.