- Community Home
- >
- Software
- >
- HPE Morpheus Software
- >
- HPE Morpheus Enterprise
- >
- Re: Datadog Plugin GovCloud compatibility
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2022 10:31 AM
10-27-2022 10:31 AM
Datadog Plugin GovCloud compatibility
Hello, first time posting to the community.
The project I’m on is interested in using the Datadog plugin which I downloaded from here:
https://share.morpheusdata.com/datadog-plugin/about
The FQDN for the Datadog front-end in GovCloud is different from the usual FQDN. The plugin currently defaults to authenticating to:
However the GovCloud endpoint for Datadog is:
https://ddog-gov.com
Looks like the source code is here:
Can an option be added in the plugin to toggle between these two endpoints?
- Tags:
- Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2022 08:26 AM
12-01-2022 08:26 AM
Re: Datadog Plugin GovCloud compatibility
Hi Martez,
Thank you for the update. I tested the new plugin v0.0.4 in our Morpheus Nonprod environment on version 5.4.12
I was able to upload the plugin, configured it for ddog-gov, and then I provisioned an instance, installed the datadog agent on the instance, but never saw a datadog tab for it in the instance view. So I went to the plugin, and clicked the checkbox for enable to uncheck and disable it. That’s when the plugin threw a gasket and now I cannot open the edit view for the plugin.
I just deleted the plugin, uploaded it again, clicked edit, and immediately tried to disable the plugin, and it threw a gasket.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2022 02:45 PM
12-01-2022 02:45 PM
Re: Datadog Plugin GovCloud compatibility
Thank you for the quick turnaround on this. I tested v0.0.5 and no longer get the error when disabling and enabling the plugin. However, after providing the API Key and the Application Key in the configuration, I don’t appear to get any Datadog tab in the instance view. The plugin doesn’t seem to indicate if it is actually attempting to communicate with the ddog-gov.com API endpoint or even the public cloud endpoint. All I see in the logs when I enable the plugin are three INFO level logs about the c.m.p.PluginManagerService:
- creating plugin permissions
- saved new plugin permission datadog-instance-tab
- registering asset pipeline class loader with prefix path /plugin/datadog-tab-plugin
When I disable the plugin I see one INFO level log for c.m.p.PluginManagerService: - deleting permission datadog-instance-tab
If I check or uncheck the GovCloud endpoint I do see an INFO level log for c.m.AuditLogService
2022-12-01_22:36:41.36275 ‘’[2022-12-01 22:37:17,617] [http-nio-127.0.0.1-8080-exec-9] INFO c.m.AuditLogService - CEF:0|MorpheusData|Morpheus|5.4.12|admin:plugins#update|plugin Updated|src=10.57.9.53 suid=2 suser=scrubbed request=http://scrubbed/admin/plugins/4 requestMethod=PUT cn1=4 cn1Label=Object ID cs1Label=Object Type cs1=plugin cn2=1 cn2Label=Account ID
2022-12-01_22:37:19.81699 ‘’[2022-12-01 22:37:32,533] [http-nio-127.0.0.1-8080-exec-7] INFO c.m.AuditLogService - CEF:0|MorpheusData|Morpheus|5.4.12|admin:plugins#update|plugin Updated|src=10.57.9.53 suid=2 suser=scrubbed request=http://scrubbed/admin/plugins/4 requestMethod=PUT cn1=4 cn1Label=Object ID cs1Label=Object Type cs1=plugin cn2=1 cn2Label=Account ID
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2022 07:17 PM
12-01-2022 07:17 PM
Re: Datadog Plugin GovCloud compatibility
Ensure that the instance where the DataDog agent is installed has the designated tag defined in the plugin settings (datadog by default). If the instance does not have the appropriate tag then the tab will not show. Additionally the Morpheus group and environment can also be used to determine the visibility of the tab. One other thing to be aware of is that you may need to log out and back in before the tab is visible in some cases.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2022 01:04 PM
11-30-2022 01:04 PM
Re: Datadog Plugin GovCloud compatibility
Thanks for posting. A new version of the DataDog plugin has been created to add support for toggling between the public and govcloud API endpoints. Currently the JAR for the new version can be downloaded from the link below while the new version is added to the Morpheus Exchange (share.morpheusdata.com).
The setting has been added to the plugin configuration settings section under API endpoint with the default being the public API endpoint but the govcloud endpoint is now a selectable option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2022 10:27 AM
12-01-2022 10:27 AM
Re: Datadog Plugin GovCloud compatibility
I’ve taken a look at the scenario you’ve mentioned and I was able to reproduce the issue. A new release (v0.0.5) of the plugin is now available that changes the drop-down list to a checkbox for those that need to use the GovCloud API endpoint instead of the public endpoint. This change addresses the issue experienced with disabling the plugin.