-
Notifications
You must be signed in to change notification settings - Fork 11
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
Issue with creating group #17
Comments
The trick with removing
|
Hmm, looks like I harcoded the kuma label name to |
I just changed it because multiple instances (servers) connect to the same uptime-kuma server. If I don't change it, it will interfere with each other. |
Should work now on latest master |
@BigBoot I'm still seeing this behavior on latest master. Could it be a combination of other factors?
Edit: I tried both parent_name as well as parent, with both Kuma and kuma. Edit 2: Below is my new go to format (for now) and I'm leaving the parent lines commented out otherwise I get an error.
|
Following up on my prior, I noted that the groups do appear to work when they are lowercase. This works
This fails
This also works, creating a capitalized group and assigning the members to the group, but I'm not sure why it works.
|
The parent_name is referring to the autokuma id of the group, not the display name, so this should work: - kuma.${AUTOKUMA_GROUP_ID_MONITORING}.group.name=${AUTOKUMA_GROUP_NAME_MONITORING}
- kuma.{{container_name}}-http.http.parent_name=${AUTOKUMA_GROUP_ID_MONITORING}
- kuma.{{container_name}}-http.http.name=Portainer HTTP
- kuma.{{container_name}}-http.http.url=http://port.$DOMAINNAME
- kuma.{{container_name}}.docker.parent_name=${AUTOKUMA_GROUP_ID_MONITORING}
- kuma.{{container_name}}.docker.name=Portainer
- kuma.{{container_name}}.docker.docker_container={{container_name}}
- kuma.{{container_name}}.docker.docker_host=1 |
Awesome, that makes sense, super helpful. Is |
It's mentioned in the usage section of the readme and is handled purely by autokuma, I added this as a way to reference other monitors as there would be no way to get the actual id from uptime kuma before creating the parent, the MONITOR_TYPES.md is generated from uptime kuma source and therefore doesn't include it. |
I'm still having problems with groups even after the last fix in #8
The only difference from sample config is that I'm using a custom tag_name:
AutoKumaL01
The group is indeed there, the name is also correct.
The text was updated successfully, but these errors were encountered: