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

Visualization not working on Azure billing dashboard #25511

Closed
pmusa opened this issue May 3, 2021 · 4 comments · Fixed by #25554
Closed

Visualization not working on Azure billing dashboard #25511

pmusa opened this issue May 3, 2021 · 4 comments · Fixed by #25554
Assignees
Labels
bug Team:Integrations Label for the Integrations team

Comments

@pmusa
Copy link

pmusa commented May 3, 2021

For confirmed bugs, please report:

  • Version: 7.12.0 (did not test other versions)
  • Steps to Reproduce: Ingest billing metrics from Azure and open the Azure Billing dashboard. The [Billing resource name] visualization will be empty.

After further investigation, I noticed that we are using a field that does not exist in the collected documents. In the visualization, we bucket on azure.resource.name, but the correct field is azure.resource.type. I also noticed that the visualization is not filtering documents that contain the field, which results in a slower aggregation (~40ms vs. ~2ms) and wrong results (see screenshots).

Bucket using azure.resource.name with no results:
Screenshot 2021-05-03 at 23 39 09

Bucket using azure.resource.type no filter with wrong results:
Screenshot 2021-05-03 at 23 40 14

Bucket using azure.resource.type and filter with correct results:
Screenshot 2021-05-03 at 23 38 26

@pmusa pmusa added the bug label May 3, 2021
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 3, 2021
@ChrsMark ChrsMark added the Team:Integrations Label for the Integrations team label May 5, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label May 5, 2021
@ChrsMark
Copy link
Member

ChrsMark commented May 5, 2021

Thanks for reporting this @pmusa!

@narph could you please verify if this is actually a bug?

@narph
Copy link
Contributor

narph commented May 5, 2021

confirmed this looks like a bug, azure.resource.name should be still there, it looks like we took it out while working on the inventory fields (replaced with cloud.instance.name), this might not have been the goal for billing as well. I will investigate this further.

@narph narph self-assigned this May 5, 2021
@narph
Copy link
Contributor

narph commented May 5, 2021

@pmusa , I have fixed the visualization in the above PR, in the visualization above we split by resource name. Maybe in the future we can add a visualization splitting on the resource type as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Team:Integrations Label for the Integrations team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants