Open ak-fusionone opened 5 months ago
This shows the truncated query:
The issue occured another time with another analytic rule query that ends with this part:
Hi team,
Is there any update on this?
Otherwise who should I contact?
Thanks for any hint
This issue is stale because it has been open for 45 days with no activity.
Is there any update on this? Otherwise who should we contact? Thanks for any hint
This issue is stale because it has been open for 45 days with no activity.
Is there any update on this?
Otherwise who should I contact?
Describe the Bug with repro steps
Hi team,
There is a bug that occurs in a specific strange condition that I noticed in a Logic App.
In order to reproduce this bug you need to create a new Analytic rule (following is a simplified example I have exported) in Sentinel:
And you need also to create a logic app that has "Microsoft Sentinel incident" as a trigger (first step). Add any random step after that since the bug remains in the first step "Microsoft Sentinel incident". Save the logic app.
You need to create a new Sentinel Automation with the "When incident is created" trigger. And you need to use the "Run Playbook" action. And you need to select the logic app you have created.
This means that when a Sentinel Incident is triggered, the logic app will retrieve the Sentinel Incident details.
The bug that I noticed is in the output provided in the first step.
If you didn't know, the Sentinel Analytic Rules are limited with around 15 000 characters in the query if I remember well. And the first step of that logic app should show all the details of the Sentinel Incident including the analytic rule query even if it reaches the 15 000 length (I have an example of output that shows the query include 15 000 characters).
But the example of analytic rule I have provided doesn't behave the same way. When a Sentinel Incident triggers, the first step of that logic app shows this:
And as you can see the query was truncated to 2975 characters. The original query was longer and no matter what is the query length, the "Microsoft Sentinel incident" step always shows 2975 characters from the query by adding "…" at the end.
Among all the long analytic rules that generated Sentinel Incident, this is the only one that shows this strange behavior.
Do I need the query? Yes it's very important.
What made me think this is exactly a bug in the logic app is that in Sentinel when I access the Incident and I click on the Entity, I can see the real query not the trucated query.
Thank you for your efforts as usual.
What type of Logic App Is this happening in?
Consumption (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
No
Workflow JSON
No response
Screenshots or Videos
No response
Browser
Version 126.0.6478.62 (Official Build) (64-bit)
Additional context
No response