[AR parser] Add preventive error handling for missing production data

[taehunlee990803]

Summary

• Enhanced the AR (Argentina) production parser with advanced error handling.
• Explicitly check if renewables or non-renewables production data is empty or invalid.
• Raise ParserException early if data is missing, preventing silent failures.
• Improve logging: added info logs for record counts and warning logs for partial data issues.

Motivation

Although the AR parser is currently working and Issue #8054 has been closed,
this PR aims to prevent future incidents where missing or invalid production data could silently pass undetected.

By ensuring the parser fails fast and clearly when data is missing,
the ElectricityMap server can detect problems immediately instead of misinterpreting the parser as healthy.

This enhances the robustness and observability of the parser and helps maintain reliable data quality over time.

Changes

• Update renewables_production_mix() and non_renewables_production_mix() to:
  • Validate HTTP response status
  • Validate JSON structure
  • Check for empty production lists
  • Gracefully handle missing fields in production items
• Improved logging for easier debugging.
• Raise ParserException if production data is missing or invalid.

Related Issues

• Related to: AR production parser down #8054 (although the original issue was closed, this prevents future similar incidents)

Checklist

• Successfully ran poetry run test_parser AR production locally and verified correct outputs.
• Verified that the parser correctly raises ParserException when API returns empty or invalid data.
• Confirmed that all added logs are meaningful, non-intrusive, and help debugging without noise.
• Focused changes only on improving parser robustness and preventive error handling.
• No unrelated changes were introduced.

[Copilot]

Pull Request Overview

This PR adds preventive error handling to the AR production parser to ensure that missing or invalid production data is caught early and handled appropriately.

• Adds enhanced error handling (timeouts, try/except blocks) for both renewables and non-renewables production data retrieval.
• Improves logging for debugging by reporting errors and warnings, and raises ParserException when necessary.

Comments suppressed due to low confidence (2)

parsers/CAMMESA.py:118

• The ParserException's 'parser' field is set to 'AR.py', which may be confusing since this file is named 'CAMMESA.py'. Consider using a consistent identifier that matches the file name to simplify debugging.

raise ParserException(parser="AR.py", message=f"Renewables API error: {str(e)}", zone_key=zone_key)

parsers/CAMMESA.py:152

• Catching a KeyError during the production record parsing only logs a warning and skips the record, which may lead to incomplete production data. Consider implementing a more robust handling strategy or accumulating and reporting these cases to ensure data integrity.

logger.warning(f"[AR Renewables] Missing expected field {e} in production info: {production_info}")

[VIKTORVAV99]

I fail to see how this solves the problems you describe. If anything it creates more points of failure and complexity as is.

Would love to discuss it more though.

[VIKTORVAV99]

This would do the opposite of your intentions here, if we set it to 0 if it's missing there is no way to know if it's actually missing or just 0 when we just look at the data so this we cant do.

[VIKTORVAV99]

Why raise for status instead of simply checking if the response is okay? with api_cammesa_response.ok and directly raise the parser exception. that way we can avoid the try except statement that adds additional overhead.

[VIKTORVAV99]

Why was this comment removed?

[VIKTORVAV99]

This will create too many logs, please remove it.

[VIKTORVAV99]

Same here as above.

[VIKTORVAV99]

this will only work for momento now as the others are accessed used get which means it won't throw any errors.