[BUG] <title>

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior


{'id': 245, 'target': 'centos.disk_free.usage', 'alertDefineId': 69, 'priority': 2, 'content': 'centos--disk_free--usage--10.0--tmpfs--184.0--1712.0--10.0--/run--{system_value_row_count}--/run', 'status': 0, 'times': 1, 'firstAlarmTime': 1693299174841, 'lastAlarmTime': 1693299174841, 'triggerTimes': 1, 'tags': {'app': 'centos', 'monitorId': '290008237707264', 'monitorName': 'CENTOS_192.168.26.35'}, 'creator': None, 'modifier': None, 'gmtCreate': [2023, 8, 29, 16, 52, 54, 844342000], 'gmtUpdate': [2023, 8, 29, 16, 52, 54, 844342000]}

告警模板的环境变量，能支持取到主机ip或者主机名称吗 或者告警模板能取到monitorName字段么

### Expected Behavior

_No response_

### Steps To Reproduce

_No response_

### Environment

```markdown
HertzBeat version(s):
```

### Debug logs

_No response_

### Anything else?

_No response_

The issue concerns alert-template environment variables for a CentOS disk alert and asks whether the host IP, host name, or monitorName can be exposed. No source file, test, or entry point is named, so start by locating alert-template variable resolution; done means the requested host identity is available in rendered alert content.

Written by the indexing model from the issue text.