Added documentation with examples to check NSM main events in logs

[ljkiraly]

Signed-off-by: Laszlo Kiraly laszlo.kiraly@est.tech

Description

Troubleshooting description for checking some events in NSM logs.

Issue link

Checklist

• Purpose
  • Bug fix
  • New functionality
  • Documentation
  • Refactoring
  • CI
• Test
  • Unit test
  • E2E Test
  • Tested manually
• Introduce a breaking change
  • Yes (description required)
  • No
• Introduce changes in the Operator
  • Yes (description required)
  • No

[uablrek]

Good addition to troubleshooting! IMHO precisely the kind of doc that should go in there. I could nitpick but I think contents is the important here (it should be easy to add things in the tr-guide) so I am ready to accept this PR with this constraint;

Drop the sub-directory. Have a flat structure will make it simpler to convert to other formats, e.g. wiki, and it is also more clear and easier to maintain unless the tr-guide grows too large. And in case of that unlikely even we can make a clean restructure when the day comes.

[uablrek]

But drop the sub-dir

[ljkiraly]

Planning to add this description to NSM. Putting this on hold till decision.

[uablrek]

Sounds good. NSM definitely needs more documentation. Please add a link in the Meridio ts-guide if you do.

[uablrek]

When the NSM log issue is fixed, Meridio will format NSM logs in json (please see #275 (comment)). The way to analyze logs will be the same but the logs will look different.