-
Notifications
You must be signed in to change notification settings - Fork 24
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
Unable to send ASM logs to a HTTP endpoint via telemetry streaming #280
Comments
Hi @harshnasitcrest, Have you tried to apply the following and fine tune memory management? |
Hi @harshnasitcrest, Can you try to disable system poller and test it? |
Referring to https://clouddocs.f5.com/products/extensions/f5-telemetry-streaming/latest/telemetry-system.html#system-poller , I disabled system poller using following declaration: "My_System_Minimal": {
"class": "Telemetry_System",
"systemPoller": {
"enable": false
}
} I increased memory and CPU both after disabling system poller. Somehow, I don't see memory and tomcat restart errors now, but I still don't see any logs regarding failures in making API call to destination. Does the last log saying |
what is your full declaration? (you can mask/remove secrets from it) |
@petrov-serg Here's the full declaration that I posted using {
"class": "Telemetry",
"My_ASM_Listener": {
"class": "Telemetry_Listener",
"port": 6514,
"trace": true,
"match": "ASM",
"actions": [
{
"setTag": {
"application": "`ASM`"
},
"enable": true
}
]
},
"My_System_Minimal": {
"class": "Telemetry_System",
"systemPoller": {
"enable": false
}
},
"My_Consumer": {
"class": "Telemetry_Consumer",
"type": "Generic_HTTP",
"host": "10.50.9.132",
"protocol": "http",
"port": 5151,
"path": "/post",
"headers": [
{
"name": "Authorization",
"value": "12345689"
},
{
"name": "ID1",
"value": "ABC"
},
{
"name": "ID2",
"value": "XYZ"
}
],
"actions": [
{
"JMESPath": {},
"expression": "{ logs: [@] }"
}
]
}
} |
Environment
Summary
I'm able to generate ASM logs deployed in our on-premise setup but unable to send it via telemetry streaming to a HTTP endpoint (consumer type is
Generic_HTTP
).Steps To Reproduce
Steps to reproduce the behavior:
/var/log/asmdata1/request_log
and shown on the F5 UI at: Security --> Events logs --> Application --> Requests.Screenshot 1:
Screenshot 2:
6. Verified that enough resources are provided for this setup to work.
Expected Behavior
The text was updated successfully, but these errors were encountered: