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
Copy file name to clipboardExpand all lines: articles/partner-solutions/elastic/manage.md
+34-51Lines changed: 34 additions & 51 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,14 @@
2
2
title: Manage settings for your Elastic resource via Azure portal
3
3
description: Manage settings, view resources, reconfigure metrics/logs, and more for your Elastic resource via Azure portal.
4
4
ms.topic: how-to
5
-
ms.date: 10/06/2023
5
+
ms.date: 03/19/2025
6
6
7
7
8
8
---
9
9
10
10
# Manage settings for your Elastic resource via Azure portal
11
11
12
-
This article shows how to manage the settings for Elastic.
12
+
This article shows how to manage the settings for Elastic resources.
13
13
14
14
## Resource overview
15
15
@@ -41,7 +41,9 @@ Below the essentials, you can navigate to other details about your resource by s
41
41
42
42
## Reconfigure rules for metrics and logs
43
43
44
-
When you created the Elastic resource, you configured which logs are sent to Elastic. If you need to change those settings, select **Metrics and Logs** in the left pane. Make the needed changes to how logs are sent to Elastic.
44
+
When you created the Elastic resource, you configured which logs are sent to Elastic. If you need to change those settings, select **Metrics and Logs** in the left pane.
45
+
46
+
Make the needed changes to how logs are sent to Elastic.
45
47
46
48
## View monitored resources
47
49
@@ -54,92 +56,73 @@ To view the list of resources emitting logs to Datadog, select **Elastic deploym
54
56
55
57
You can install Datadog agents on virtual machines.
56
58
57
-
## Monitor virtual machines using Elastic agent
58
-
59
-
You can install Elastic agents on virtual machines as an extension. To see the available virtual machines in your subscription, select **Virtual Machines** from the left pane of your Elastic resource.
60
-
61
-
For each virtual machine, the following data is displayed:
62
-
63
-
- Resource Name – Virtual machine name.
64
-
- Resource Status – Whether the virtual machine is stopped or running. The Elastic agent can only be installed on virtual machines that are running. If the virtual machine is stopped, installing the Elastic agent is disabled.
65
-
- Agent version – The Elastic agent version number.
66
-
- Agent status – Whether the Elastic agent is running on the virtual machine.
67
-
- Integrations enabled – The key metrics collected by the Elastic agent.
68
-
- Sending logs – Whether the Elastic agent is sending logs to Elastic.
69
-
70
-
To install the Elastic agent, select a virtual machine and select **Install Extension**.
59
+
### Virtual machines
71
60
72
-
The portal asks for confirmation that you want to install the agent with the default authentication. Select **OK** to begin installation. The portal shows the status as **Installing** until the agent is installed and provisioned.
61
+
To monitor resources for virtual machines, select **Elastic deployment configuration > Virtual machine agent** in the Resource menu.
73
62
74
-
After the Elastic agent is installed, the status changes to **Installed**.
To see that the Elastic agent is installed, select the virtual machine and navigate to **Extensions**.
65
+
## Connect Azure OpenAI service with Elastic
77
66
78
-
To uninstall the Elastic agent on a virtual machine, select the virtual machine and **Uninstall Extension**.
67
+
To configure Azure Open AI, select **Elastic deployment configuration > Azure OpenAI configuration**.
79
68
80
-
## Configure diagnostic settings
69
+
1. From the working pane's command bar, select **Add**.
81
70
82
-
To configure the diagnostic settings for a resource, select that resource. In the left pane, select **Diagnostic settings**.
71
+
1. In the *Add OpenAI Configuration* panel, select your preferred **Azure OpenAI Resource** and **Azure OpenAI Deployment**.
83
72
84
-
In the destination details section, check the option to send to partner solutions to select Elastic as a destination target. The option is only available after an Elastic resource is created.
73
+
1. Select the **Create** button.
85
74
86
-
## Configure Azure OpenAI Connector
75
+
Once the Connector is created, navigate to Kibana.
87
76
88
-
If not configured already while creating the resource, you can navigate to **Azure OpenAI configuration** under the Elastic deployment configuration section. Select on **Add** to select the Azure OpenAI (AOAI) resource and a deployment of a text/chat completion model(like gpt4), making your connector ready without having to switch contexts between the AOAI resource (in Azure portal) and the Connectors page in Elastic portal, thus avoiding having to copy and paste urls and keys.
89
-
90
-
Select on **Create**.
91
-
92
-
Once the Connector is created, navigate to Kibana and search for Connectors under Stack Management. The newly created Azure OpenAI Connector should be visible there. This connector can be used within Elastic's Observability AI Assistant to help provide contextual responses to your natural language prompts on your observability data by invoking the Azure OpenAI deployment. Learn more about Elastic OpenAI Connectors [here](https://www.elastic.co/guide/en/kibana/current/openai-action-type.html).
77
+
> [!NOTE]
78
+
>
79
+
> Kiabana is a user interface that lets you visualize your Elasticsearch data and navigate the Elastic Stack. Your Connector can be used within Elastic's Observability AI Assistant to help provide contextual responses to your natural language prompts on your observability data by invoking the Azure OpenAI deployment.
93
80
94
81
## Private link management
95
82
96
-
You can limit network access to a [private link](../../private-link/private-link-overview.md). To enable private link access, select **Configuration** in the left navigation. Under **Networking**, select **Private Link** and the name of the private link.
83
+
You can limit network access to a private link.
97
84
98
-
:::image type="content" source="media/manage/private-link.png" alt-text="Screenshot of enabling private link":::
85
+
To enable privatelink access:
99
86
100
-
## Traffic filters
87
+
1. Select **Configuration** in the left navigation.
88
+
1.
89
+
1. Under **Networking**, select **Private Link** and the name of the private link.
101
90
102
-
To manage how Elastic deployments can be accessed, you can set Traffic filters for Azure Private Links.
91
+
## Traffic filters
103
92
104
-
:::image type="content" source="media/manage/elastic-traffic-filter.png" alt-text="Screenshot showing Traffic Filter selected in the Resource menu.":::
93
+
To manage how Elastic deployments can be accessed, set Traffic filters for Azure Private Links.
105
94
106
95
There are two types of filters available:
107
96
108
97
- IP traffic filter
109
98
- Private Link traffic filter
110
99
111
-
Select **Add** to set up and automatically associate a new traffic filter to and Elastic deployment.
100
+
Select **Add** to set up and automatically associate a new traffic filter to an Elastic deployment.
112
101
113
-
To associate an already existing traffic filter to the current deployment, you select **Link**. The traffic filter must be in the same region as the deployment.
102
+
To associate an already existing traffic filter to the current deployment, you select **Link**.
103
+
104
+
> [!IMPORTANT]
105
+
> The traffic filter must be in the same region as the deployment.
114
106
115
107
If a traffic filter is no longer needed, unlink it from deployment and then delete it.
116
108
117
109
## Connected Elastic resources
118
110
119
111
To access all Elastic resources and deployments you created using the Azure or Elastic portal experience, go to the **Connected Elastic resources** tab in any of your Azure Elastic resources.
120
112
121
-
:::image type="content" source="media/manage/connected-elastic-resources.png" alt-text="Screenshot showing Connected Elastic resources selected in the Resource menu.":::
122
-
123
113
You can easily manage the corresponding Elastic deployments or Azure resources using the links, provided you have owner or contributor rights to those deployments and resources.
124
114
125
115
## Delete Elastic resource
126
116
127
-
When you no longer need your Elastic resource, delete the resource in the Azure portal.
128
-
129
-
> [!IMPORTANT]
130
-
> Deleting an Elastic resource stops billing only for the corresponding Elastic deployment.
> A single Azure Marketplace SaaS unifies billing for multiple Elastic deployments. If you're looking to completely stop billing for the marketplace SaaS, you need to delete all linked Elastic deployments (created from Azure or Elastic portal). Deleting the Azure subscription or resource group corresponding to marketplace SaaS doesn't guarantee billing stop and doesn't clean up corresponding Elastic deployments.
134
-
135
-
To delete the resource in Azure, select your Elastic resource. In **Overview**, select **Delete**. Confirm that you want to delete Elastic resource.
136
-
137
-
:::image type="content" source="media/manage/delete-elastic.png" alt-text="Screenshot of delete Elastic resource.":::
138
-
139
-
When the Elastic resource is deleted, logs are no longer sent to Elastic. All billing stops for Elastic through Azure Marketplace.
120
+
>
121
+
> - A single Azure Marketplace SaaS unifies billing for multiple Elastic deployments.
122
+
> - If you wish to completely stop billing for the marketplace SaaS, delete all linked Elastic deployments (created from Azure or Elastic portal).
140
123
141
124
## Related content
142
125
143
126
-[Troubleshooting Elastic integration with Azure](troubleshoot.md)
0 commit comments