[DOCS-14104] [OM] Document lastPing endpoint Created: 07/Jan/21  Updated: 17/May/22  Resolved: 04/Feb/21

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: Kanchana Sekhar
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 3 years, 6 days ago
Epic Link: DOCSP-7540
Story Points: 3

 Description   

Description

There have been multiple support cases where customers requested a way to access lastPing data via API.

There is in fact an endpoint for that:

GET /api/public/v1.0/groups/<PROJECT_ID>/hosts/<HOST_ID>/lastPing

As per MMS-1781, it was a deliberate decision to leave it undocumented as the format of the lastPing data is not documented.

It is an opinion of TSEs that the endpoint should still be mentioned in the documentation (with a caveat that the data format it retrieves can change from version to version). That would help us deflect customer support cases more easily.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Kanchana Sekhar [ 04/Feb/21 ]

Based on discussions with melissa.plunkett, I understand this needs to first go through prod triage before this is addressed in the doc. Please feel free to re-open if/when this is needed. Thanks!

Comment by Melissa Plunkett [ 04/Feb/21 ]

dmitry.ryabtsev can you provide an example of the multiple support cases. Engineering made this decision some time ago and I'm sure we can at least look at it again but we'd need to know what kind of impact it's had or if the solution that worked for apple cited in the MMS may be a longer term workaround.

Generated at Thu Feb 08 08:09:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.