-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Monitoring] Change cloud messaging on no data page #88375
[Monitoring] Change cloud messaging on no data page #88375
Conversation
Pinging @elastic/stack-monitoring (Team:Monitoring) |
For messaging we can use something like [Configure monitoring through Elasticsearch Service Console. Go to Logs and metrics section for a deployment to configure monitoring. For more information visit the documentation page.] We can add deep links as much as available. |
How about: |
If it's easy to update the message then it would helpful. I tried to use terms that are used elsewhere (Elasticsearch service console) and provides more specific information (logs and metrics) where to go for configuring monitoring. |
@ravikesarwani Yea I don't think we can truly deep link but we can link to the deployments page and we have total control over the messaging you see in the screenshot. Happy to change it to whatever you want. Just lemme know |
How about this? |
Thanks, looks good. Short and sweet. |
Sorry, was wondering if we should change the top message "Monitoring is currently off" in the Cloud since we do not know if monitoring is enabled. All we know that there's no monitoring data to show. Maybe we change that top message to say "Monitoring data not available". WDYT? |
WDYT? |
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍
* WIP * Update tests * Update copy * Fix translations and update copy * Fix tests and update copy
* WIP * Update tests * Update copy * Fix translations and update copy * Fix tests and update copy
* master: (33 commits) [Security Solution][Case] Fix patch cases integration test with alerts (elastic#88311) [Security Solutions][Detection Engine] Removes duplicate API calls (elastic#88420) Fix log msg (elastic#88370) [Test] Add tag cloud visualization to dashboard in functional test for reporting (elastic#87600) removing kibana-core-ui from codeowners (elastic#88111) [Alerting] Migrate Event Log plugin to TS project references (elastic#81557) [Maps] fix zooming while drawing shape filter logs errors in console (elastic#88413) Porting fixes 1 (elastic#88477) [APM] Explicitly set environment for cross-service links (elastic#87481) chore(NA): remove mocha junit ci integrations (elastic#88129) [APM] Only display relevant sections for rum agent in service overview (elastic#88410) [Enterprise Search] Automatically mock shared logic files (elastic#88494) [APM] Disable Create custom link button on Transaction details page for read-only users [Docs] clean-up vega map reference documenation (elastic#88487) [Security Solution] Fix Timeline event details layout (elastic#88377) Change DELETE to POST for _bulk_delete to avoid incompatibility issues (elastic#87914) [Monitoring] Change cloud messaging on no data page (elastic#88375) [Uptime] clear ping state when PingList component in unmounted (elastic#88321) [APM] Consistent terminology for latency and throughput (elastic#88452) fix copy (elastic#88481) ...
Relates to #85990
In #85990, we noticed that cloud has officially migrated from legacy collection to Metricbeat collection and we need to take away the option for users to enable legacy collection in the UI.