training

To improve visibility and debugging of charging sessions and audit events, we need to enhance the existing APIs to include machine name and connector number along with the connector_id.

Currently, APIs such as:

charging-session/{session_id}

audit-log?ruleName=Energy+Anomaly

only return the connector_id, which makes it difficult for support and operations teams to quickly identify the actual machine and connector used in the session.

The API responses should be enhanced to include a human-readable format combining machine name and connector number.

Proposed Format

Display connector information in the following format:

Machine Name (Connector Number)

Example:

120kWh Machine (14)

Where:

Machine Name: Retrieved from the machine table

Connector Number: Retrieved from the connector table using connector_id

Scope of Work

Update API response for:

charging-session/{session_id}

audit-log?ruleName=Energy+Anomaly

Fetch related information:

Machine Name

Connector Number

Connector ID

Add a new response field such as:

connector_display_name

Example response:

{
"connector_id": 14,
"machine_name": "120kWh Machine",
"connector_number": 14,
"connector_display_name": "120kWh Machine (14)"
}

Ensure the enhancement does not impact existing API consumers.

Acceptance Criteria

charging-session/{session_id} API returns machine name and connector number.

audit-log API for ruleName=Energy Anomaly returns the same connector information.

Connector information should appear in the format Machine Name (Connector Number).

Existing API functionality remains unaffected.