| 2021-08-03 13:44:04 |
Arif Ali |
bug |
|
|
added bug |
| 2021-08-03 19:25:58 |
Billy Olsen |
description |
Hi,
As of mitaka the pipeline-yaml configuration option does not work, and therefore users/customers are not able to specify their own customised pipeline.
A new option was added to add remote-sink, which allowed to add multiple remote sinks to the configuration.
I am proposing 2 things
1. Update the config.yaml to update the pipeline-yaml config option, so that it says that this option is only supported pre-mitaka
2. The customer in question was trying to use pipeline-yaml to add a different sink other than remote or event sinks, i.e. meter_sink. So I am suggesting we add a new configuration option i.e. meter-sink which would add something very similar to what remote-sink does.
Below is an excerpt from what the customer was trying to attempt with the pipeline-yaml configuration option
sources:
- name: 'meter source'
meters:
- '*'
sinks:
- 'meter_sink'
sinks:
- name: 'meter_sink'
transformers:
publishers:
- http://X.X.X.X:8080/telegraf?timeout=10&max_retries=2&batch=False |
Hi,
As of mitaka the pipeline-yaml configuration option does not work, and therefore users/customers are not able to specify their own customised pipeline.
A new option was added to add remote-sink, which allowed to add multiple remote sinks to the configuration.
I am proposing 2 things
1. Update the config.yaml to update the pipeline-yaml config option, so that it says that this option is only supported pre-mitaka
2. The user in question was trying to use pipeline-yaml to add a different sink other than remote or event sinks, i.e. meter_sink. So I am suggesting we add a new configuration option i.e. meter-sink which would add something very similar to what remote-sink does.
Below is an excerpt from what the user was trying to attempt with the pipeline-yaml configuration option
sources:
- name: 'meter source'
meters:
- '*'
sinks:
- 'meter_sink'
sinks:
- name: 'meter_sink'
transformers:
publishers:
- http://X.X.X.X:8080/telegraf?timeout=10&max_retries=2&batch=False |
|
| 2021-08-03 19:26:07 |
Billy Olsen |
description |
Hi,
As of mitaka the pipeline-yaml configuration option does not work, and therefore users/customers are not able to specify their own customised pipeline.
A new option was added to add remote-sink, which allowed to add multiple remote sinks to the configuration.
I am proposing 2 things
1. Update the config.yaml to update the pipeline-yaml config option, so that it says that this option is only supported pre-mitaka
2. The user in question was trying to use pipeline-yaml to add a different sink other than remote or event sinks, i.e. meter_sink. So I am suggesting we add a new configuration option i.e. meter-sink which would add something very similar to what remote-sink does.
Below is an excerpt from what the user was trying to attempt with the pipeline-yaml configuration option
sources:
- name: 'meter source'
meters:
- '*'
sinks:
- 'meter_sink'
sinks:
- name: 'meter_sink'
transformers:
publishers:
- http://X.X.X.X:8080/telegraf?timeout=10&max_retries=2&batch=False |
Hi,
As of mitaka the pipeline-yaml configuration option does not work, and therefore users are not able to specify their own customised pipeline.
A new option was added to add remote-sink, which allowed to add multiple remote sinks to the configuration.
I am proposing 2 things
1. Update the config.yaml to update the pipeline-yaml config option, so that it says that this option is only supported pre-mitaka
2. The user in question was trying to use pipeline-yaml to add a different sink other than remote or event sinks, i.e. meter_sink. So I am suggesting we add a new configuration option i.e. meter-sink which would add something very similar to what remote-sink does.
Below is an excerpt from what the user was trying to attempt with the pipeline-yaml configuration option
sources:
- name: 'meter source'
meters:
- '*'
sinks:
- 'meter_sink'
sinks:
- name: 'meter_sink'
transformers:
publishers:
- http://X.X.X.X:8080/telegraf?timeout=10&max_retries=2&batch=False |
|
| 2021-08-10 18:21:31 |
OpenStack Infra |
charm-ceilometer: status |
New |
In Progress |
|
| 2021-08-10 19:33:44 |
Arif Ali |
tags |
|
sts |
|
| 2021-08-10 19:34:08 |
Arif Ali |
charm-ceilometer: assignee |
|
Arif Ali (arif-ali) |
|
| 2021-08-13 23:14:26 |
OpenStack Infra |
charm-ceilometer: status |
In Progress |
Fix Committed |
|
| 2021-08-13 23:21:13 |
Billy Olsen |
charm-ceilometer: milestone |
|
21.10 |
|
| 2021-08-18 08:04:59 |
Arif Ali |
charm-ceilometer: assignee |
Arif Ali (arif-ali) |
|
|
| 2021-10-22 13:26:54 |
Alex Kavanagh |
charm-ceilometer: status |
Fix Committed |
Fix Released |
|
| 2021-11-05 10:15:12 |
Aurelien Lourot |
charm-ceilometer: milestone |
21.10 |
22.04 |
|
| 2021-11-05 10:15:15 |
Aurelien Lourot |
charm-ceilometer: status |
Fix Released |
Fix Committed |
|
| 2021-11-05 10:24:25 |
Aurelien Lourot |
charm-ceilometer: status |
Fix Committed |
In Progress |
|
| 2021-11-05 10:24:37 |
Aurelien Lourot |
charm-ceilometer: milestone |
22.04 |
21.10 |
|
| 2021-11-05 10:45:29 |
Aurelien Lourot |
charm-ceilometer: milestone |
21.10 |
22.04 |
|
| 2021-11-05 10:45:34 |
Aurelien Lourot |
charm-ceilometer: status |
In Progress |
Fix Committed |
|
| 2022-05-10 16:47:35 |
Alex Kavanagh |
charm-ceilometer: status |
Fix Committed |
Fix Released |
|
| 2023-07-13 19:50:38 |
Felipe Reyes |
nominated for series |
|
charm-ceilometer/ussuri |
|
| 2023-07-13 19:50:38 |
Felipe Reyes |
bug task added |
|
charm-ceilometer/ussuri |
|
| 2023-07-13 19:50:38 |
Felipe Reyes |
nominated for series |
|
charm-ceilometer/victoria |
|
| 2023-07-13 19:50:38 |
Felipe Reyes |
bug task added |
|
charm-ceilometer/victoria |
|
| 2023-07-13 19:50:38 |
Felipe Reyes |
nominated for series |
|
charm-ceilometer/wallaby |
|
| 2023-07-13 19:50:38 |
Felipe Reyes |
bug task added |
|
charm-ceilometer/wallaby |
|
| 2023-07-13 19:50:38 |
Felipe Reyes |
nominated for series |
|
charm-ceilometer/xena |
|
| 2023-07-13 19:50:38 |
Felipe Reyes |
bug task added |
|
charm-ceilometer/xena |
|
