Skip to content
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

No "un-install" doc for logging tools #4118

Closed
ckden opened this issue Sep 29, 2021 · 10 comments
Closed

No "un-install" doc for logging tools #4118

ckden opened this issue Sep 29, 2021 · 10 comments
Labels
content requests related to docs site content docs-issues from_external Identifies issues/PRs from non-Relics Jira'd This issue generated a Jira issue to track this internally.

Comments

@ckden
Copy link

ckden commented Sep 29, 2021

Tell us what you need

Hi, first great job on explaining and documenting the various ways to bring data into New Relic logging. However, once these things are setup, the process to unwind them does not seem to be easy to identify. In particular, if I have a application team who is sending log test data to the logs.API (For example), it would be helpful to have something documented that app teams could follow to understand how to unconfigure a log ingestion cleanly.

we have several apps teams who need help with this and I am unable to provide a simple answer since each is using different methods to ingest log info.

Thank you for your consideration of this request.

Anything else you'd like to share?

Most of your other products have an uninstall or removal feature defined through documentation, adding this would be more consistent and help teams avoid ingestion of log information that is no longer needed.

Doc information (don't delete this section)

@github-actions github-actions bot added this to Hero to triage in Docs PRs and Issues Sep 29, 2021
@bradleycamacho
Copy link
Contributor

Hey @ckden, thanks for the very thoughtful feedback! This is a great call, and we can explore documenting this with our product teams. I am going to tag in @barbnewrelic, one of our docs writers with more context about logs.

@bradleycamacho bradleycamacho moved this from Hero to triage to Hero: To do in Docs PRs and Issues Sep 29, 2021
@bradleycamacho bradleycamacho added content requests related to docs site content from_external Identifies issues/PRs from non-Relics pg_TDP labels Sep 29, 2021
@barbnewrelic
Copy link
Contributor

@ckden I reviewed our backlog of log doc requests and discovered this was on the roadmap 2 years ago, but then the team decided not to document uninstall procedures at that time. Thanks for raising this issue again. I'll get it back into the queue!

@barbnewrelic barbnewrelic moved this from Hero: To do to Writer needs peer edit (Hero or any TW can take) in Docs PRs and Issues Oct 1, 2021
@barbnewrelic barbnewrelic moved this from Writer needs peer edit (Hero or any TW can take) to Waiting on SME/Blocked in Docs PRs and Issues Oct 1, 2021
@barbnewrelic
Copy link
Contributor

@ckden Do you only need procedures to uninstall/stop Log API, or are there other log forwarders your teams currently use? There are several different ways to get logs into New Relic, and the logging SMEs want to prioritize the ones you use first. Thanks for confirming!

@ckden
Copy link
Author

ckden commented Oct 6, 2021

@barbnewrelic , thanks for the follow up and sorry for slow reply. I did some checking and because we have fairly diverse environment teams are making use of all the different methods currently, with the infrastructure agent being used the most. So, if it helps I would say infra. would be the one that would help me the most immediately. Thank you!

@barbnewrelic
Copy link
Contributor

@ckden We are happy you are using so many options for logs, and we are also sad that uninstall procedures never got documented. I'm going to file a ticket for the documentation work, but I don't think I can file a support ticket on your behalf to get immediate help from support. I've already notified them about your question, but I wonder if it would help expedite if the request for immediate assistance was coming directly from you as a support ticket? I do apologize to give you extra work, but I don't want to keep you waiting on our docs team. The uninstall procedures will have to come from our tech support engineers, and we will then be able to use their solutions to publish in the documentation site. I hope this gives you the help you need for the short term!

@barbnewrelic barbnewrelic added the Jira'd This issue generated a Jira issue to track this internally. label Oct 7, 2021
@ckden
Copy link
Author

ckden commented Oct 13, 2021

Hi again @barbnewrelic , understood and no problem. I will open one this evening as a follow up to this thread. Thank you.

@barbnewrelic
Copy link
Contributor

I notified support to be on the lookout for your ticket, and I'll link it to my docs work. Thanks again!

@ckden
Copy link
Author

ckden commented Oct 15, 2021

HI, Thanks and sorry for short delay on getting it opened, but it is now open > https://support.newrelic.com/tickets/474211/edit

@barbnewrelic
Copy link
Contributor

@ckden I got the uninstall info from support and added it to the infra logs forwarder doc. https://docs.newrelic.com/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/#uninstall . I'm still tracking down how to uninstall all the other log forwarders, but is this sufficient for now? (I have a Jira to address all the log forwarders, so your request won't be lost.) If you're satisfied with this doc update and my ongoing plan, I'll go ahead and close this issue. If not, I'm happy to keep this issue open. Let me know what works best for you. Thanks again for working so patiently both with support and with me!

@barbnewrelic
Copy link
Contributor

Added info to all the other log forwarder docs with #6280

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content requests related to docs site content docs-issues from_external Identifies issues/PRs from non-Relics Jira'd This issue generated a Jira issue to track this internally.
Projects
None yet
Development

No branches or pull requests

3 participants