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

Telemetry Fails on Azure Clouds Other Than AzurePublic and AzureUSGovernment #213

Closed
blheatwole opened this issue Aug 11, 2022 · 3 comments · May be fixed by #216
Closed

Telemetry Fails on Azure Clouds Other Than AzurePublic and AzureUSGovernment #213

blheatwole opened this issue Aug 11, 2022 · 3 comments · May be fixed by #216
Labels
bug Something isn't working untriaged Issue needs to be reviewed for validity

Comments

@blheatwole
Copy link

Environment

  • Telemetry Streaming Version: 1.30
  • BIG-IP Version: BIG-IP 16.1.2.2 Build 0.0.28 Point Release 2

Summary

The URLs to send telemetry to Azure are hard-coded and limited to AzurePublic and AzureUSGovernment. See

function getApiDomain(region, apiType) {

Steps To Reproduce

Steps to reproduce the behavior:

  1. Install F5-telemetry in AzureGerman, AzureChina, AzureSecret or some other Azure cloud that is not AzurePublic or AzureUSGovernment.
  2. Configure F5-telemetry to send to Log Analytics: https://clouddocs.f5.com/products/extensions/f5-telemetry-streaming/latest/setting-up-consumer.html#microsoft-azure-log-analytics

Expected Behavior

Logs are streamed to Log Analytics

Actual Behavior

F5 Telemetry attempts to ship the logs to 'azure.com' which (if accessible) does not know about the Log Analytics workspace and the request fails.

@blheatwole blheatwole added bug Something isn't working untriaged Issue needs to be reviewed for validity labels Aug 11, 2022
@blheatwole
Copy link
Author

Please add an optional configuration value where we can directly set the management and op insights URLs.

Note that in some clouds the actual URLs used cannot be publicly published, and so relying solely on hard-coded values can never support all clouds/regions.

@mdditt2000
Copy link

Created TS-697 for PM tracking

@blheatwole
Copy link
Author

I'm cleaning up the docs and tests to submit a PR for this later today

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged Issue needs to be reviewed for validity
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants