[DOCS-14325] jq log processing examples should be simplified Created: 31/Mar/21 Updated: 07/Feb/24 |
|
| Status: | Internal Review |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Nic Cottrell | Assignee: | Kenneth Dyer |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | backlog, request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 24 weeks, 1 day ago | ||||
| Epic Link: | DOCSP-11702 | ||||
| Description |
DescriptionAt https://docs.mongodb.com/manual/reference/log-messages/ there are a lot of examples with jq including the pattern . | select(...) for example:
However, it appears that this isn't necessary and the following has identical behaviour:
I'm no jq expert, so probably good to validate all example to make sure there's no edge case that does require the {{. | }} option. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Alex Bevilacqua [ 23/Aug/22 ] |
|
nicholas.cottrell@mongodb.com I reviewed for torsten.spindler@mongodb.com on https://docs.google.com/document/d/1Jf3jLrqOFBvP0pX6rcMsttPgkYcUpbd461bb7og3L5U/edit, so based on this he may be the best candidate. |
| Comment by Nic Cottrell [ 22/Aug/22 ] |
|
Not sure about priority, but in terms of an expert maybe alex.bevilacqua@mongodb.com can be of assistance here, or point us to our internal expert on jq? |