Skip to content

Support avelon cloud api - #84

Closed
therapac wants to merge 13 commits into
Linuxfabrik:mainfrom
StadtLuzernIO:support_avelon_cloud_api
Closed

therapac wants to merge 13 commits into
Linuxfabrik:mainfrom
StadtLuzernIO:support_avelon_cloud_api

Conversation

@therapac

Copy link
Copy Markdown

The Avelon library was created to communicate with the Avelon Cloud API. It provides three public functions: get_token, get_ticket, and get_data_points. The get_token and get_ticket functions should be fully complete. However, the get_data_points function still lacks detailed error handling. This will be addressed with the upcoming Avelon_XY (data_points) monitoring plugin. Despite this, functional tests have been conducted across all functions.

@markuslf
markuslf self-requested a review June 25, 2024 06:02
markuslf added a commit to Linuxfabrik/monitoring-plugins that referenced this pull request Sep 18, 2026
Reimplements #771 and Linuxfabrik/lib#84
along our current standards, keeping their logic and their fixtures.

- Uses /public-api/v2/tickets; v1 is gone from the OpenAPI document.
- Asks per device (filterScope DEVICE), since DeviceTO no longer
  carries a clientId, and in parallel.
- Requests unclosed tickets back to 2000-01-01: without beginDate the
  API returns only tickets modified within seven days, so an untouched
  open alarm would drop out after a week (from the docs, not measured).
- Covers all nine ticket statuses and three ticket types.
- Keeps the Avelon access in the plugin, as it has a single consumer.
@markuslf

Copy link
Copy Markdown
Member

Thank you. The Avelon access now lives in the avelon-tickets plugin itself (Linuxfabrik/monitoring-plugins@a71ff5e7af), since it has a single consumer so far. It moves into the lib once a second Avelon check needs it. Closing in favour of that.

@markuslf markuslf closed this Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants