You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Send event logs directly to Azure Log Analytics Workspace (LAW)
Problem
We deploy intermediate resources to accept web hooks from FusionAuth and relay audit, event, and login record events to LAW. This has several downsides in our opinion:
The intermediate results in additional maintenance, costs, monitoring, and risks of failure during the collection process
Webhooks cannot be retried in case of failures and interruptions. If not mitigated by elaborate additional log collection via FusionAuth API and duplication handling, this could result in missing data in LAW.
Solution
Implement a solution to connect FusionAuth to an Azure Log Analytics Workspace and robustly ingest event logs directly. This mitigates additional resources, logic, maintenance, costs, and points of failure.
Alternatives/workarounds
The FusionAuth documentation also suggests using Apache Kafka in combination with a no-op webhook receiver that discards incoming POST requests and returns 200. This approach is non-suitable for us for maintenance and architectural reasons.
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
The text was updated successfully, but these errors were encountered:
Send event logs directly to Azure Log Analytics Workspace (LAW)
Problem
We deploy intermediate resources to accept web hooks from FusionAuth and relay audit, event, and login record events to LAW. This has several downsides in our opinion:
Solution
Implement a solution to connect FusionAuth to an Azure Log Analytics Workspace and robustly ingest event logs directly. This mitigates additional resources, logic, maintenance, costs, and points of failure.
Alternatives/workarounds
The FusionAuth documentation also suggests using Apache Kafka in combination with a no-op webhook receiver that discards incoming POST requests and returns 200. This approach is non-suitable for us for maintenance and architectural reasons.
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.
How to vote
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
The text was updated successfully, but these errors were encountered: