-
Notifications
You must be signed in to change notification settings - Fork 185
Code crash while querying for notification endpoint #243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@bednar Can you please help? |
Hi @abhi1693, it looks like that a schema generated by the OpenAPI generator is not correct. We will take a look. Regards |
@bednar Is there any ETA on this? Our complete development is on hold again |
We don't have ETA, but Today I will start working on this. Can you describe your usecase, please? It will be useful for us to be sure that we are deliver correct solution for you. |
We want to use the client library to create, edit, delete and view alerts.
This would mean management of the notification rules as well as the
endpoints.
…On Fri, 7 May, 2021, 11:17 am Jakub Bednář, ***@***.***> wrote:
We don't have ETA, but Today I will start working on this. Can you
describe your usecase, please? It will be useful for us to be sure that we
are deliver correct solution for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#243 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZDDF4V63XDYD6VQSTQ4DTMN5H5ANCNFSM44CWZ3MA>
.
|
@bednar Any progress on this? |
@bednar We have a deadline on a project. Can you please give an ETA otherwise we will think of some other way to manage the notification stack? |
Hi @abhi1693, sorry for late. I don't have exact ETA for you, but today I've start working on this issue. As a workaround you can directly call InfluxDB API by something like this: from influxdb_client import InfluxDBClient
url = "http://localhost:8086"
token = "my-token"
org_id = "my-org-id"
with InfluxDBClient(url=url, token=token, org=org_id) as client:
query_params = [('orgID', org_id)]
notificationEndpoints = client.api_client.call_api('/api/v2/notificationEndpoints',
'GET',
query_params=query_params,
response_type=object)[0]
print(notificationEndpoints)
notificationRules = client.api_client.call_api('/api/v2/notificationRules',
'GET',
query_params=query_params,
response_type=object)[0]
print(notificationRules) Regards |
Hi @abhi1693, there is an upcoming fix for Monitoring & Alerting API - #261. You can try the dev version by:
and there is also an corresponding example: https://github.com/influxdata/influxdb-client-python/blob/feat/swagger-update/examples/monitoring_and_alerting.py Regards |
Steps to reproduce:
We are trying to fetch the notification endpoints. Here is the minimal code
I have masked the
org_id
. The underlying issue could be tied to an incorrect schema. Since there is little to no documentation on generating and verifying the code using the open API schema, I was unable to determine the root cause.Expected behaviour:
The API should return the endpoint list.
Actual behaviour:
Specifications:
The text was updated successfully, but these errors were encountered: