Skip to content

[O365_metrics] Add active_users_services_user_counts Dashboard #14232

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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

lucian-ioan
Copy link
Contributor

@lucian-ioan lucian-ioan commented Jun 16, 2025

Proposed commit message

Add active_users_services_user_counts dashboard.

I think active/inactive graphs bar charts work fine. For it to have only one graph and a control at the top, the data structure would need to be a different format.

Having one bar chart/other vis for each specific service seems unnecessary since this data has a fixed number of only 6 services.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • Update other dashboards descriptions hyperlinks.
  • Push data into elasticsearch to simulate active counts and more than one report.

How to test this PR locally

Related issues

Screenshots

image

@lucian-ioan lucian-ioan self-assigned this Jun 16, 2025
@lucian-ioan lucian-ioan added dashboard Relates to a Kibana dashboard bug, enhancement, or modification. Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations] Integration:o365_metrics Microsoft Office 365 Metrics labels Jun 16, 2025
@lucian-ioan lucian-ioan marked this pull request as ready for review June 17, 2025 10:12
@lucian-ioan lucian-ioan requested a review from a team as a code owner June 17, 2025 10:12
@elastic-vault-github-plugin-prod
Copy link

elastic-vault-github-plugin-prod bot commented Jun 17, 2025

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

💚 Build Succeeded

History

cc @lucian-ioan

Copy link

Copy link
Contributor

@Linu-Elias Linu-Elias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should hide the y-axis labels as we have multiple services
image

@muthu-mps
Copy link
Contributor

@lucian-ioan - The Report Last Refresh Date in the metrics panel, how this is helpful when the dashboard time range is selected for last 15 mins or 1 hour? Can this be in a table view?

@lucian-ioan
Copy link
Contributor Author

@muthu-mps Report Last Refresh Date is showing how recent the data is. In other words, when was the data last updated which I think is useful to know.

Instead of a table view, perhaps a control on Report Refresh Date is more useful if we want users to filter data based on that while also seeing all of the dates the refreshes happened.

@ritalwar
Copy link
Contributor

Instead of a table view, perhaps a control on Report Refresh Date is more useful if we want users to filter data based on that while also seeing all of the dates the refreshes happened.

I've noticed that the existing report based dashboards in the package include control over the report refresh date. I think we should maintain the same experience for other report-based dashboards as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dashboard Relates to a Kibana dashboard bug, enhancement, or modification. Integration:o365_metrics Microsoft Office 365 Metrics Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants