EIP provides the following O&M and Monitoring features:
Cost optimization: Automatically identify long-term unused resources by managing idle instances to prevent unnecessary costs.
Granular management: Use tags to categorize resources across multiple dimensions, enabling cost allocation and automated O&M.
Auditing and traceability: Track historical changes by viewing operation records to meet security audit and fault isolation requirements.
Manage idle instances
Manage EIPs that remain unassociated with a cloud resource for a specified idle period. You can then release them, associate them with other resources, or add them to a whitelist to manage costs for unused resources.
Check idle status
View idle instances:
Go to the Idle Instance page.
Set Resource Type to Elastic IP Addresses to view idle EIPs. By default, the Idle Period is 7 Days. You can change this value in the Idle Period drop-down list to view instances that have been idle for 3 or 14 days.
Set idle notifications: When an instance's idle time exceeds the duration you set, the system sends a notification. This helps you stay informed about idle instances and manage them promptly.
On the Idle Instance page, click Set Alert for Idle Status. For Elastic IP Addresses, turn on the switch in the Alert for Idle Status column and set the Idle Duration (Day). You can configure recurring notifications, which are sent every time the specified idle duration passes.
Handle idle instances
Release resources: For resources you no longer need, click Release in the Actions column.
Associate with a resource: Click Associated Instance in the Actions column, select the instance type and the specific instance, and then associate the EIP with the specified cloud resource.
Add to a whitelist: For EIPs that must be retained long-term but are not in active use, such as reserved IPs, disaster recovery (DR) IPs, or fixed egress IPs, you can add them to a whitelist. The system does not send idle notifications for whitelisted instances.
Manage tags
Use tags to label and categorize EIPs, build a business-oriented resource view, and make it easier to search and aggregate resources.
Tagging best practices.
Usage notes
Quota: You can associate a maximum of 20 tags to a single EIP. This quota cannot be increased.
Security: Do not include sensitive information, such as passwords or AccessKey pairs, in tags. Tag information may appear in plaintext on your billing statements.
Conventions:
Each tag consists of a key-value pair. Tag keys and values are case-sensitive. Keys cannot start with the prefixes
aliyun,acs:,http://, orhttps://.Each tag key must be unique for a single instance.
Tags must be associated with an instance and cannot exist as standalone entities.
Tags are specific to a region and are not shared across regions. For example, a tag created in the China (Hangzhou) region is not visible in the China (Shanghai) region.
You can modify the key and value of a tag, or remove tags from an instance. When an instance is deleted, all tags associated with it are also deleted. This does not affect tags associated with other instances.
Add or remove tags
Manage a single EIP: Go to the EIP page. In the Tags column for the target EIP, hover over the
icon and click Bind or Edit in the pop-up. To delete a key-value pair, click the 
icon next to it.If the Tags column is not displayed, click the
icon in the upper-right corner of the EIP list to customize the displayed columns.Manage tags in batches: Select one or more EIPs. In the lower-left corner of the page, choose Configure Tags>Batch Add Tags or Configure Tags>Batch Delete Tags.
Filter by tag: Above the list, click Filter by Tag, and then select or enter a key-value pair to filter the list.
View operation records
The operation records feature uses ActionTrail to log the change history of EIPs. This helps you quickly identify misconfigurations or abnormal activities.
Go to the EIP page.
Click the ID of the target EIP and select the Operation Records tab to view its operation records. You can click View Details for more information or filter the records by Event Name or Time Range.
Scope: Records write operations on your Alibaba Cloud account performed through the console, API calls, or developer tools.
Time window:
Instant query: You can view operation records from the last 1h, 12h, 1d, 7d, 30d, or a Custom time range directly in the console. Records are available for the last 90 days.
Long-term compliance: To store logs for more than 90 days for compliance purposes, configure an ActionTrail trail to deliver the logs to Log Service (SLS) or Object Storage Service (OSS).