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

Legacy Fortinet Connector cannot be deleted #10166

Open
roboftheblues opened this issue Mar 18, 2024 · 18 comments
Open

Legacy Fortinet Connector cannot be deleted #10166

roboftheblues opened this issue Mar 18, 2024 · 18 comments
Assignees
Labels
Connector Connector specialty review needed

Comments

@roboftheblues
Copy link

Despite the fact that the OMS agent has been removed from the Linux VM, the legacy connector still shows 'Connected' and cannot be deleted. I understand that this is deprecated in August 2024 but we should be able to disconnect and delete it. We have already installed the CEF AMA Connector.

@v-sudkharat v-sudkharat added the Connector Connector specialty review needed label Mar 18, 2024
@v-sudkharat
Copy link
Contributor

v-sudkharat commented Mar 18, 2024

Hi @roboftheblues, The data connector has their own Connectivity Criteria, and it is in sync with the Log Analytic Workspace. The query will check the expected result in the LAW and based on that the connect status will get displayed.
Ex. If you run below data connector connectivity criteria query into your workspace and if you get result as True, it means your connector will show up as Connected for that time period -

CommonSecurityLog| where DeviceVendor == "Fortinet"| where DeviceProduct startswith "Fortigate" | summarize LastLogReceived = max(TimeGenerated) | project IsConnected = LastLogReceived > ago(7d)

image

In addition, you cannot delete the data connector once it gets installed into the workspace.
Please let us know if we resolve your issue, so we can close it from GitHub.
Thanks!

@roboftheblues
Copy link
Author

That doesn't show which connector it is. We also have the CEF AMA Connector connected to the log forwarder which is collecting logs from the Fortinet Firewall

@v-sudkharat
Copy link
Contributor

Hey @roboftheblues, Could you please share more context about the connector or the expected behavior. As per your issue description it's looks you are having below 2 CEF connector is configured but not getting from where the log's get pull.
image

Thanks!

@roboftheblues
Copy link
Author

We are expecting the CEF AMA connector to collect logs from the log forwarder in accordance with the configured DCR. All tests passed but the connector does not collect the logs. The logs are present on the log forwarder and being updated but not collected.

@v-sudkharat
Copy link
Contributor

Hi @roboftheblues, Thanks for your response, we will check on the issue and will update you.
Thanks!

@v-sudkharat
Copy link
Contributor

That doesn't show which connector it is. We also have the CEF AMA Connector connected to the log forwarder which is collecting logs from the Fortinet Firewall

Hey @roboftheblues, Could you please check the "CollectorHostName" column having data into your workspace, If it contains the data for it then your CEF AMA Connector is configured.
You can run below query: -

CommonSecurityLog
|where DeviceVendor =~ 'Fortinet' 
|where DeviceProduct =~ 'Fortigate'   
|extend sent_by_ama = column_ifexists('CollectorHostName','')
| project sent_by_ama

Select the timestamp as custom to get the result. and let us know the result for it.
Thanks!

@v-sudkharat
Copy link
Contributor

Hi @roboftheblues, waiting for your response on above comment. Thanks!

@roboftheblues
Copy link
Author

roboftheblues commented Apr 2, 2024 via email

@v-sudkharat
Copy link
Contributor

@roboftheblues, Noted. Please let us know anything need from us. Thanks!

@v-sudkharat
Copy link
Contributor

Hi @roboftheblues, Waiting for your response. Thanks!

@roboftheblues
Copy link
Author

roboftheblues commented Apr 9, 2024 via email

@v-sudkharat
Copy link
Contributor

@roboftheblues, Noted.

@roboftheblues
Copy link
Author

Sorry, didn't realise my email address came out wrong here!
robwood894@hotmail.com

@roboftheblues
Copy link
Author

Please feel free to add a meeting to my calendar for next week. I am on CET

@roboftheblues
Copy link
Author

Waiting for a response from you, i need to discuss the issues with the fortinet connectors and the CEF AMA connector

@v-sudkharat
Copy link
Contributor

Hey @roboftheblues, Need some more time to repro this issue :- #10146 in our environment.
And regrading this issue :- #10166, We have shared the query on in this comment (#10166 (comment)) to know which connector has been configured.

Thanks!

@roboftheblues
Copy link
Author

CollectorHostName isn't being sent

@v-sudkharat
Copy link
Contributor

@roboftheblues, Noted. Let us check on this and will share update with you. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connector Connector specialty review needed
Projects
None yet
Development

No branches or pull requests

3 participants