Grouping Medusa Widget Breaks #4499
Unanswered
kevjustice
asked this question in
Support
Replies: 2 comments
-
there is no difference between widgets in this way. Perhaps check your yaml formatting |
Beta Was this translation helpful? Give feedback.
0 replies
-
Found the issue that I wasn't aware of. Groups and sub-groups need to be unique! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
I tried the new services grouping feature and it seems great, however the Medusa widget does not work when it's in a sub group. I decided to replicate it in the group, not the subgroup and the exact same configuration works in a group.
I have a hunch that your widget code does not search for sub-groups and fails to find the group of the name. Just a theory...
Note: I have suppressed the full IP and keys in logs/configs.
homepage version
v0.10.5
Installation method
Docker
Configuration
Container Logs
Nothing in logs related to that ip/port.
Browser Logs
XHRGET
http://10.10.1.YY:3000/api/siteMonitor?groupName=Services&serviceName=Medusa2
[HTTP/1.1 400 Bad Request 122ms]
GET
http://10.10.1.YY:3000/api/siteMonitor?groupName=Services&serviceName=Medusa2
Status
400
Bad Request
VersionHTTP/1.1
Transferred280 B (56 B size)
Referrer Policystrict-origin-when-cross-origin
DNS ResolutionSystem
Troubleshooting
To assist troubleshooting, I renamed the 2nd Medusa to Medusa2. It wass the one that caused the browser log.
Beta Was this translation helpful? Give feedback.
All reactions