Difference between revisions of "Azure Log Analytics"
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
# In a browser, go the Azure portal, locate your Log Analytics workspace. | # In a browser, go the Azure portal, locate your Log Analytics workspace. | ||
# Select Advanced Settings and then Connected Sources. | # Select Advanced Settings and then Connected Sources. | ||
| − | # Under the "WORKSPACE ID" label, select the [https://en.wikipedia.org/wiki/Universally_unique_identifier GUID], copy and then paste it into the <code>LogAnalyticsWorkspaceID</code> element in <code>TruxtonSettings.xml</code>. | + | # Under the "WORKSPACE ID" label, select the [https://en.wikipedia.org/wiki/Universally_unique_identifier GUID], copy and then paste it into the <code>LogAnalyticsWorkspaceID</code> element in <code>[[Configuration_System#Truxton_Settings_File|TruxtonSettings.xml]]</code>. |
| − | # Under the "PRIMARY KEY" label, select the text, copy and then paste it into the <code>APIKey</code> element in <code>TruxtonSettings.xml</code>. | + | # Under the "PRIMARY KEY" label, select the text, copy and then paste it into the <code>APIKey</code> element in <code>[[Configuration_System#Truxton_Settings_File|TruxtonSettings.xml]]</code>. |
| − | # Save <code>TruxtonSettings.xml</code> | + | # Save <code>[[Configuration_System#Truxton_Settings_File|TruxtonSettings.xml]]</code> |
===Sample Config File=== | ===Sample Config File=== | ||
Latest revision as of 13:20, 27 July 2022
AKA
Log Analytics has also been known as:
- Operational Insights
- Monitor
Creation
In order to begin playing with Azure Log Analytics, you must first create a Log Analytic Workspace (aka Operational Insights Workspace). To do that, you must first have a Resource Group.
- Go the Home page of Azure Portal
- In the "Search resources" edit control at the top of the page, type "Log Analytics" then select "Log Analytics workspaces" from the results.
- Click the "+ Add" button in the top menu bar
- Give the new workspace a name (truxlaw)
- Select the Subscription
- Select the Resource Group (truxlogs)
- Select the Location. For best results, use the same location as the Resource Group (US East or US East 2)
- Click OK
- Azure will go off and think about what you've done for a while, then tell you it succeeded. Wait a minute or two and refresh the web page to see the new workspace listed.
Keys and ID
In order for Truxton to log forensic items to Azure Monitor service, it must know where to send the log messages.
- Edit the
TruxtonSettings.xmlfile in the "C:\ProgramData\Truxton\Settings" folder. - Under the
truxton_optionselement, create a new element namedAzureMonitor - Under the
AzureMonitorelement, create a new element namedLogAnalyticsWorkspaceID - Under the
AzureMonitorelement, create a new element namedAPIKey - In a browser, go the Azure portal, locate your Log Analytics workspace.
- Select Advanced Settings and then Connected Sources.
- Under the "WORKSPACE ID" label, select the GUID, copy and then paste it into the
LogAnalyticsWorkspaceIDelement inTruxtonSettings.xml. - Under the "PRIMARY KEY" label, select the text, copy and then paste it into the
APIKeyelement inTruxtonSettings.xml. - Save
TruxtonSettings.xml
Sample Config File
<?xml version="1.0" encoding="utf-8"?>
<truxton_options>
<AzureMonitor>
<LogAnalyticsWorkspaceID>7d70d995-c49d-43f2-80d0-1253ef811c73</LogAnalyticsWorkspaceID>
<APIKey>YxNXhS8oXCjTXp87DMpEZAcLv5od3dTaSR0xzm3xzQWT7svsytJ/WQyyejLn9lbxI4VbM/ByzuTV8dgqW0V2eg==</APIKey>
</AzureMonitor>
<dbserver>localhost</dbserver>
<dbport>5432</dbport>
<dbname>Truxton</dbname>
<dbuser>postgres</dbuser>
<dbpassword>password</dbpassword>
<mqserver>localhost</mqserver>
<mqport>5432</mqport>
<mqname>TruxtonMessageBus</mqname>
<mquser>postgres</mquser>
<mqpassword>password</mqpassword>
<datadir>C:\Truxton Data</datadir>
<machineid>9D29E664-A4F2-48C3-88D2-BCF7CB5DEBBC</machineid>
<CreateTheDatabase>1</CreateTheDatabase>
<solr_url>http://localhost:8983/solr/truxton-core</solr_url>
</truxton_options>
References
- az - You can create a log analytic workspace using:
az monitor log-analytics workspace create