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

Follow up for issue #196 regarding to KEDA scaling detail logs #941

Open
yansyunchen opened this issue Oct 16, 2023 · 1 comment
Open

Follow up for issue #196 regarding to KEDA scaling detail logs #941

yansyunchen opened this issue Oct 16, 2023 · 1 comment
Labels
Needs: triage 🔍 Pending a first pass to read, tag, and assign

Comments

@yansyunchen
Copy link

In the issue here (#196), it seems we are able to get he KEDA details log in ContainerAppSystemLogs_CL. But from my test lab, I cannot see any details insides. Would like to know if these log would exist or not? Thank you

May I know is possible to see "which metric" to trigger the scaling event on the ContainerAppSystemLogs_CL?
From my personal lab, I have rule below:
image

But it seems I cannot see any related scaling event detail in the ContainerAppSystemLogs_CL. (E.g. Scaling up cuz of cpu>1)
ContainerAppSystemLogs_CL
//| where EventSource_s == "KEDA"
| where RevisionName_s == "container-app-power--0cuzw05"
| take 100
| project TimeGenerated, Type_s, Log_s, RevisionName_s, ContainerAppName_s, EventSource_s, Reason_s
query_data.csv

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 Pending a first pass to read, tag, and assign label Oct 16, 2023
@chlsmith
Copy link

I would love to see more KEDA logs in Log Analytics, too. I see when the scaler is started or stopped, and if I have a config error it will sometimes show up in Log Analytics. However, if there are other issues with KEDA itself keeping my container from scaling, I cannot see them. Using a github-runner scaler right now and I cannot get it to scale at all. My initial container deploys and registers as a runner, but none of the scaling works regardless of the level I register the runners. If I could see the KEDA logs to find out what it's looking for and finding from the github API, I could troubleshoot more in-depth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: triage 🔍 Pending a first pass to read, tag, and assign
Projects
None yet
Development

No branches or pull requests

2 participants