Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] <Does monitorHost in the message notification template refer to the resource IP> #1508

Closed
1 task done
hiqumin opened this issue Jan 22, 2024 · 2 comments · Fixed by #1515
Closed
1 task done
Assignees
Labels
good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested
Milestone

Comments

@hiqumin
Copy link

hiqumin commented Jan 22, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

在企业微信机器人的消息通知模版中想显示资源IP,配置monitorHost字段不生效。
image

Expected Behavior

No response

Steps To Reproduce

No response

Environment

HertzBeat version(s):

Debug logs

No response

Anything else?

No response

@hiqumin hiqumin added the bug Something isn't working label Jan 22, 2024
@hertzbeat hertzbeat changed the title [BUG] <消息通知模版中monitorHost指的是资源IP吗> [BUG] <Does monitorHost in the message notification template refer to the resource IP> Jan 22, 2024
@tomsun28 tomsun28 added good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested and removed bug Something isn't working labels Jan 23, 2024
@tomsun28
Copy link
Contributor

hi, we do not has the monitorHost variable default. We can consider support it after.

@UdayRajVadeghar
Copy link

i dont think there is any "monitorHost" variable.

@tomsun28 tomsun28 added this to the 1.4.5 milestone Jan 24, 2024
@tomsun28 tomsun28 linked a pull request Jan 26, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants