Dos l7 report via IControl Rest Api

[Milos007_323731]

Is it possible to generate report for dos l7 with icontrol rest api? I have found following end-pint /mgmt/tm/analytics/dos-l7/report/ which always gave me a message 'You must enter a view-by entity name'. What is 'view-by' entity?

On next link https://devcentral.f5.com/wiki/iControlREST.APIRef_tm_analytics_dos-l7_report.ashx I have found that '~resource id' is followed by'report'. What is that resource id? Can anyone show me an example?

Best Regards M

[diaoxueping_318]

i have the same question. do you resolve this question?

[Madhu_Rajagopal]

The view-by option follows the tmsh command syntax and includes the following for dos-l7:

tmsh show analytics dos-l7 report view-by:

• application
• client-subnet
• device-id
• dosl7-bot-signature
• dosl7-profile
• pool-member
• transaction-outcome
• user-agent
• client-ip
• country
• dosl7-attack-id
• dosl7-bot-signature-category
• method
• response-code
• url
• virtual

TMSH reference manual: page 139 - https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-tmsh-reference-12-0-0.pdf

To access one of these, here are a few examples using curl: * virtual curl -ksu admin:changeme https://10.154.170.18/mgmt/tm/analytics/dos-l7/report?options=view-by,virtual

• application curl -ksu admin:changeme https://10.154.170.18/mgmt/tm/analytics/dos-l7/report?options=view-by,application

• pool-member curl -ksu admin:changeme https://10.154.170.18/mgmt/tm/analytics/dos-l7/report?options=view-by,pool-member

• url, limit curl -ksu admin:changeme https://10.154.170.18/mgmt/tm/analytics/dos-l7/report?options=view-by,url,limit,200

[Michal_Seckar_3]

Hello , how can i use range command/filter please? now--5m like in cli does not work with http api.. 😞 thx Im after what format i need to use, there is no any documentation at all..

[Nikoolayy1]

Still valid even for asm cpu reports:

mgmt/tm/analytics/asm-cpu/report?options=view-by,virtual,measures,%7Bbd-cpu-utlization%7D

I got  the idea from this post thanks! As measures use {}, it needs special encoding.