Skip to content

Conversation

@leifmadsen
Copy link
Member

  • Describe the sensubility Smart Gateway object in the ServiceTelemetry manifest

Resolves rhbz#2008338

  • Update doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc

  • Update doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc

Cherry picked from commit a4eda65
Co-authored-by: JoanneOFlynn2018 45287002+JoanneOFlynn2018@users.noreply.github.com

… manifest (#301)

* Describe the sensubility Smart Gateway object in the ServiceTelemetry manifest

Resolves rhbz#2008338

* Update doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc

* Update doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc

Cherry picked from commit a4eda65
Co-authored-by: JoanneOFlynn2018 <45287002+JoanneOFlynn2018@users.noreply.github.com>
@leifmadsen leifmadsen added cherry-pick Needs cherry-pick to stable branches 1.3 labels Sep 29, 2021
@leifmadsen leifmadsen enabled auto-merge (squash) September 29, 2021 13:04
@leifmadsen leifmadsen disabled auto-merge September 29, 2021 17:53
@leifmadsen leifmadsen enabled auto-merge (squash) September 29, 2021 17:53
Use the `clouds` parameter to control which Smart Gateway objects are deployed, thereby providing the interface for multiple monitored cloud environments to connect to an instance of {ProjectShort}. If a supporting backend is available, then metrics and events Smart Gateways for the default cloud configuration are created. By default, the Service Telemetry Operator creates Smart Gateways for `cloud1`.

You can create a list of cloud objects to control which Smart Gateways are created for the defined clouds. Each cloud consists of data types and collectors. Data types are `metrics` or `events`. Each data type is made up of a list of collectors and the message bus subscription address. Available collectors are `collectd` and `ceilometer`. Ensure that the subscription address for each of these collectors is unique for every cloud, data type, and collector combination.
You can create a list of cloud objects to control which Smart Gateways are created for the defined clouds. Each cloud consists of data types and collectors. Data types are `metrics` or `events`. Each data type is made up of a list of collectors, the message bus subscription address, and whether debugging is enabled. Available collectors for metrics are `collectd`, `ceilometer`, and `sensubility`. Available collectors for events are `collectd` and `ceilometer`. Ensure that the subscription address for each of these collectors is unique for every cloud, data type, and collector combination.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
You can create a list of cloud objects to control which Smart Gateways are created for the defined clouds. Each cloud consists of data types and collectors. Data types are `metrics` or `events`. Each data type is made up of a list of collectors, the message bus subscription address, and whether debugging is enabled. Available collectors for metrics are `collectd`, `ceilometer`, and `sensubility`. Available collectors for events are `collectd` and `ceilometer`. Ensure that the subscription address for each of these collectors is unique for every cloud, data type, and collector combination.
You can create a list of cloud objects to control which Smart Gateways are created for the defined clouds. Each cloud consists of data types and collectors. Data types are `metrics` or `events`. Each data type is made up of a list of collectors, the message bus subscription address, and a debugging status. Available collectors for metrics are `collectd`, `ceilometer`, and `sensubility`. Available collectors for events are `collectd` and `ceilometer`. Ensure that the subscription address for each of these collectors is unique for every cloud, data type, and collector combination.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a little awkwardly worded

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs to be changed in master first and then backported. This is just a cherry-pick from master which was reviewed and merged by Joanne. If we make changes here we'll cause a regression in the next release.

@leifmadsen leifmadsen merged commit 78a17a0 into stable-1.3 Sep 29, 2021
@leifmadsen leifmadsen deleted the stf13/cp-a4eda658a8b64c215b039a6d2be61ca56c364660 branch September 29, 2021 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-pick Needs cherry-pick to stable branches

Development

Successfully merging this pull request may close these issues.

4 participants