# Frequenz Reporting API
[](https://github.com/frequenz-floss/frequenz-api-reporting/actions/workflows/ci.yaml)
[](https://pypi.org/project/frequenz-api-reporting/)
[](https://frequenz-floss.github.io/frequenz-api-reporting/)
## Introduction
Frequenz gRPC API to aggregate component data from microgrids.
## Supported Platforms
The following platforms are officially supported (tested):
- **Python:** 3.11
- **Operating System:** Ubuntu Linux 20.04
- **Architectures:** amd64, arm64
## Overview
The Microgrid Reporting API serves as an interface for obtaining detailed insights into
microgrid operations and metrics. Unlike general telemetry APIs, this API specializes in
generating reports based on complex, user-defined aggregations of microgrid data. It
provides both historical and real-time reporting capabilities.
## Objective
The primary objective of the Microgrid Reporting API is to furnish a robust foundation for
building data-driven applications that optimize microgrid performance, enable efficient
power trading strategies, and facilitate intelligent decision-making across multiple
operational scenarios. By aggregating and streamlining access to key metrics and data,
this API not only aids in conducting in-depth performance analysis but also supports the
development of algorithms and strategies for real-time and future power trading. This dual
focus ensures that the API serves as a versatile tool for both operational and financial
optimization within the microgrid ecosystem.
## Key Features
- Real-time and Historical Reporting: Supports both real-time reporting through data
streams and historical data retrieval, offering comprehensive analytical capabilities.
- Custom Aggregation: Support for user-defined aggregation formulas for microgrid
component metrics like power, voltage, and more.
- Multiple Microgrid Support: Allows users to aggregate data from multiple microgrids
in a single request, providing a holistic view of operations.
## Scope and Limitations
The Microgrid Reporting API is designed to offer extensive reporting capabilities, allowing
for both simple and complex data aggregations across multiple microgrids. It provides
granular insights on a per-component basis as well as an overarching view of entire microgrid
operations. The scope of the API is limited by the types of aggregation formulas it supports,
potentially constraining its utility in highly specialized analytical scenarios.
## Target Audience
The Microgrid Reporting API is tailored for a broad audience, including performance analysts,
trading strategists, and cloud application developers. Whether the aim is to perform in-depth
performance analysis, devise trading strategies based on microgrid data, or build applications
that capitalize on real-time and historical data, this API serves as a comprehensive data source.
By providing an array of key metrics and aggregation features, it accommodates various
use-cases and empowers users to make well-informed decisions in different operational
contexts.
## Contributing
If you want to know how to build this project and contribute to it, please
check out the [Contributing Guide](CONTRIBUTING.md).
Raw data
{
"_id": null,
"home_page": null,
"name": "frequenz-api-reporting",
"maintainer": null,
"docs_url": null,
"requires_python": "<4,>=3.11",
"maintainer_email": null,
"keywords": "frequenz, python, api, grpc, protobuf, rpc, reporting, cloud, microgrid",
"author": null,
"author_email": "Frequenz Energy-as-a-Service GmbH <floss@frequenz.com>",
"download_url": "https://files.pythonhosted.org/packages/7f/11/7c72dde83e385ab9f98273b6c1b7503c375d2b840a6ecf132a2e506bdd66/frequenz-api-reporting-0.2.0.tar.gz",
"platform": null,
"description": "# Frequenz Reporting API\n\n[](https://github.com/frequenz-floss/frequenz-api-reporting/actions/workflows/ci.yaml)\n[](https://pypi.org/project/frequenz-api-reporting/)\n[](https://frequenz-floss.github.io/frequenz-api-reporting/)\n\n## Introduction\n\nFrequenz gRPC API to aggregate component data from microgrids.\n\n## Supported Platforms\n\nThe following platforms are officially supported (tested):\n\n- **Python:** 3.11\n- **Operating System:** Ubuntu Linux 20.04\n- **Architectures:** amd64, arm64\n\n## Overview\nThe Microgrid Reporting API serves as an interface for obtaining detailed insights into\nmicrogrid operations and metrics. Unlike general telemetry APIs, this API specializes in\ngenerating reports based on complex, user-defined aggregations of microgrid data. It\nprovides both historical and real-time reporting capabilities.\n\n## Objective\nThe primary objective of the Microgrid Reporting API is to furnish a robust foundation for\nbuilding data-driven applications that optimize microgrid performance, enable efficient\npower trading strategies, and facilitate intelligent decision-making across multiple\noperational scenarios. By aggregating and streamlining access to key metrics and data,\nthis API not only aids in conducting in-depth performance analysis but also supports the\ndevelopment of algorithms and strategies for real-time and future power trading. This dual\nfocus ensures that the API serves as a versatile tool for both operational and financial\noptimization within the microgrid ecosystem.\n\n## Key Features\n- Real-time and Historical Reporting: Supports both real-time reporting through data\n streams and historical data retrieval, offering comprehensive analytical capabilities.\n- Custom Aggregation: Support for user-defined aggregation formulas for microgrid\n component metrics like power, voltage, and more.\n- Multiple Microgrid Support: Allows users to aggregate data from multiple microgrids\n in a single request, providing a holistic view of operations.\n\n## Scope and Limitations\nThe Microgrid Reporting API is designed to offer extensive reporting capabilities, allowing\nfor both simple and complex data aggregations across multiple microgrids. It provides\ngranular insights on a per-component basis as well as an overarching view of entire microgrid\noperations. The scope of the API is limited by the types of aggregation formulas it supports,\npotentially constraining its utility in highly specialized analytical scenarios.\n\n## Target Audience\nThe Microgrid Reporting API is tailored for a broad audience, including performance analysts,\ntrading strategists, and cloud application developers. Whether the aim is to perform in-depth\nperformance analysis, devise trading strategies based on microgrid data, or build applications\nthat capitalize on real-time and historical data, this API serves as a comprehensive data source.\nBy providing an array of key metrics and aggregation features, it accommodates various\nuse-cases and empowers users to make well-informed decisions in different operational\ncontexts.\n\n## Contributing\n\nIf you want to know how to build this project and contribute to it, please\ncheck out the [Contributing Guide](CONTRIBUTING.md).\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Frequenz gRPC API to aggregate component data from microgrids",
"version": "0.2.0",
"project_urls": {
"Changelog": "https://github.com/frequenz-floss/frequenz-api-reporting/releases",
"Documentation": "https://frequenz-floss.github.io/frequenz-api-reporting/",
"Issues": "https://github.com/frequenz-floss/frequenz-api-reporting/issues",
"Repository": "https://github.com/frequenz-floss/frequenz-api-reporting",
"Support": "https://github.com/frequenz-floss/frequenz-api-reporting/discussions/categories/support"
},
"split_keywords": [
"frequenz",
" python",
" api",
" grpc",
" protobuf",
" rpc",
" reporting",
" cloud",
" microgrid"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "8fd4ac047d11844deb44e373ba0e2a2ff163271ac3f88e5667ad564384094692",
"md5": "84deb728fd7b0cb67adc7208ab4d4575",
"sha256": "ab3325e851a7ab375908b698b28d91c5a1b472dc33a850b7405ba4bfdcdfa96b"
},
"downloads": -1,
"filename": "frequenz_api_reporting-0.2.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "84deb728fd7b0cb67adc7208ab4d4575",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": "<4,>=3.11",
"size": 17494,
"upload_time": "2024-04-24T12:50:08",
"upload_time_iso_8601": "2024-04-24T12:50:08.881471Z",
"url": "https://files.pythonhosted.org/packages/8f/d4/ac047d11844deb44e373ba0e2a2ff163271ac3f88e5667ad564384094692/frequenz_api_reporting-0.2.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "7f117c72dde83e385ab9f98273b6c1b7503c375d2b840a6ecf132a2e506bdd66",
"md5": "2565d3a0eb1e468c0c04082a375499e7",
"sha256": "d64b62eb7ce0ccb5a9f2cdaa5389a2070d039236229df1270588c5ac7e7594bd"
},
"downloads": -1,
"filename": "frequenz-api-reporting-0.2.0.tar.gz",
"has_sig": false,
"md5_digest": "2565d3a0eb1e468c0c04082a375499e7",
"packagetype": "sdist",
"python_version": "source",
"requires_python": "<4,>=3.11",
"size": 100484,
"upload_time": "2024-04-24T12:50:17",
"upload_time_iso_8601": "2024-04-24T12:50:17.559461Z",
"url": "https://files.pythonhosted.org/packages/7f/11/7c72dde83e385ab9f98273b6c1b7503c375d2b840a6ecf132a2e506bdd66/frequenz-api-reporting-0.2.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-04-24 12:50:17",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "frequenz-floss",
"github_project": "frequenz-api-reporting",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "frequenz-api-reporting"
}
JSON
