minor changes

Author: mahesh-tier1app

Dockerfile.base.alpine

@@ -14,6 +14,6 @@ RUN apk add --no-cache \
 
 ENV PATH=${PATH}:/usr/local/go/bin
 
-WORKDIR  /opt/workspace/yc-agent
+WORKDIR  /opt/workspace/yc-360-script
 
 ENTRYPOINT ["/bin/sh"]

Makefile

@@ -6,17 +6,17 @@ _:
 	echo "default"
 
 alpine:
-	docker build -f Dockerfile.base.alpine -t yc-agent-base:alpine .
+	docker build -f Dockerfile.base.alpine -t yc-360-script-base:alpine .
 
 base: alpine
-	docker rm -f yc-agent-alpine || true
+	docker rm -f yc-360-script-alpine || true
 	docker run --init -d -ti --rm \
-	--name yc-agent-alpine \
-	-v $(CWD):/opt/workspace/yc-agent \
-	yc-agent-base:alpine
+	--name yc-360-script-alpine \
+	-v $(CWD):/opt/workspace/yc-360-script \
+	yc-360-script-base:alpine
 
 shell:
-	docker exec -it yc-agent-alpine /bin/sh
+	docker exec -it yc-360-script-alpine /bin/sh
 
 build:
-	docker exec -it yc-agent-alpine /bin/sh -c "cd cmd/yc && go build -o yc -ldflags='-s -w' -buildvcs=false && mkdir -p ../../bin/ && mv yc ../../bin/"
+	docker exec -it yc-360-script-alpine /bin/sh -c "cd cmd/yc && go build -o yc -ldflags='-s -w' -buildvcs=false && mkdir -p ../../bin/ && mv yc ../../bin/"

README.md

@@ -1,12 +1,12 @@
 # yc-360 Script: One Script to Capture 360° Production Artifacts
 [![License](https://img.shields.io/badge/license-Apache%202.0-orange.svg)](LICENSE)
-[![Docs](https://img.shields.io/badge/yc--360%20Script-Documentation-green)](https://test.docs.ycrash.io/ycrash-agent/launch-modes/only-capture-mode.html)
+[![Docs](https://img.shields.io/badge/yc--360%20Script-Documentation-green)](https://docs.ycrash.io/yc-360/launch-modes/only-capture-mode.html)
 
 ![img](/docs/images/360-degree.png)
 
 ## What is yc-360 Script?
 
-**yc-360 script** is a simple script that captures 16 different artifacts from your application in a [pristine manner](https://test.docs.ycrash.io/ycrash-agent/features/pristine-capture.html), which are highly useful to troubleshoot production problems. Here is the list of artifacts captured by the script:
+**yc-360 script** is a simple script that captures 16 different artifacts from your application in a [pristine manner](https://docs.ycrash.io/yc-360/features/pristine-capture.html), which are highly useful to troubleshoot production problems. Here is the list of artifacts captured by the script:
 
 | **Artifact**          | **What It Captures**                                                                 |
 |-----------------------|--------------------------------------------------------------------------------------|
@@ -39,7 +39,7 @@
 
 ## Getting Started - How to run the yc-360 Script?
 
-It’s easy to get started with the yc-360 script. Just follow the simple steps provided in our [Getting Started Guide](https://test.docs.ycrash.io/ycrash-agent/launch-modes/only-capture-mode.html). In a matter of seconds, you’ll be able to trigger the script and collect all the critical artifacts needed for troubleshooting.
+It’s easy to get started with the yc-360 script. Just follow the simple steps provided in our [Getting Started Guide](https://docs.ycrash.io/yc-360/launch-modes/only-capture-mode.html). In a matter of seconds, you’ll be able to trigger the script and collect all the critical artifacts needed for troubleshooting.
 
 Whether you're running on Linux, Windows, Mac, Docker, K8, … the guide walks you
 through the setup and execution process.
@@ -61,7 +61,7 @@ Please refer to any one of the following links if you want to build the yc-360-s
 <details>
   <summary><strong>1. What if I Want to Capture Additional Data that yc-360 Script Doesn’t Collect by Default?</strong></summary>
 
-You can extend the functionality using the [`-edScript` argument](https://test.docs.ycrash.io/ycrash-agent/features/extended-data.html). This lets you specify a custom script that yc-360 script will execute as the final step, allowing you to capture additional logs, metrics, or custom files specific to your environment.
+You can extend the functionality using the [`-edScript` argument](https://docs.ycrash.io/yc-360/features/extended-data.html). This lets you specify a custom script that yc-360 script will execute as the final step, allowing you to capture additional logs, metrics, or custom files specific to your environment.
 </details>
 
 <details>
@@ -84,7 +84,7 @@ Absolutely. The yc-360 script is a non-intrusive, read-only script. It doesn’t
 <details>
   <summary><strong>4. Can yc-360 Script be executed in containerized environments like Docker, Kubernetes, or OpenShift?</strong></summary>
 
-Yes, yc-360 script is designed to work seamlessly across all major environments — including bare-metal servers, virtual machines, Docker containers, Kubernetes, and OpenShift. You can execute the script directly inside your containers or use it as part of a sidecar or init container to collect diagnostic data. For detailed guidance on each supported environments, visit [https://test.docs.ycrash.io/ycrash-agent/environment/introduction.html](https://test.docs.ycrash.io/ycrash-agent/environment/introduction.html)
+Yes, yc-360 script is designed to work seamlessly across all major environments — including bare-metal servers, virtual machines, Docker containers, Kubernetes, and OpenShift. You can execute the script directly inside your containers or use it as part of a sidecar or init container to collect diagnostic data. For detailed guidance on each supported environments, visit [https://docs.ycrash.io/yc-360/environment/introduction.html](https://docs.ycrash.io/yc-360/environment/introduction.html)
 </details>
 
 <details>

internal/agent/agent.go

@@ -25,7 +25,7 @@ func Run() error {
 
 	// Validation: if no mode is specified (neither M3, OnDemand, nor API Mode), abort here
 	if !onDemandMode && !apiMode && !m3Mode {
-		logger.Log("WARNING: M3 mode is not enabled. API mode is not enabled. Agent is about to run OnDemand mode but no PID is specified.")
+		logger.Log("WARNING: M3 mode is not enabled. API mode is not enabled. The yc-360 script is about to run OnDemand mode but no PID is specified.")
 
 		return ErrNothingCanBeDone
 	}
@@ -64,8 +64,8 @@ func Shutdown() {
 }
 
 func startupLogs() {
-	logger.Log("yc agent version: " + executils.SCRIPT_VERSION)
-	logger.Log("yc script starting...")
+	logger.Log("yc-360 script version: " + executils.SCRIPT_VERSION)
+	logger.Log("yc=360 script starting...")
 
 	msg, ok := common.StartupAttend()
 	logger.Log(

internal/agent/m3/m3.go

@@ -197,8 +197,8 @@ func GetM3CommonEndpointParameters(timestamp string, timezone string) string {
 }
 
 func (m3 *M3App) captureAndTransmit(pids map[int]string, endpoint string) (err error) {
-	logger.Log("yc agent version: " + executils.SCRIPT_VERSION)
-	logger.Log("yc script starting in m3 mode...")
+	logger.Log("yc-360 script version: " + executils.SCRIPT_VERSION)
+	logger.Log("yc-360 script starting in m3 mode...")
 
 	logger.Log("Starting collection of top data...")
 	capTop := &capture.Top4M3{}
@@ -356,7 +356,7 @@ func uploadThreadDumpM3(endpoint string, pid int, sendPidParam bool) {
 		capThreadDump.SetEndpointParam("pid", strconv.Itoa(pid))
 	}
 	capThreadDump.SetEndpointParam("cpuCount", strconv.Itoa(runtime.NumCPU()))
-	
+
 	threadDump = capture.GoCapture(endpoint, capture.WrapRun(capThreadDump))
 	// -------------------------------
 	//     Log Thread dump

internal/agent/ondemand/ondemand.go

@@ -783,7 +783,7 @@ Resp: %s
 		}
 		agentLogFile = nil
 		logger.Log(
-			`AGENT LOG DATA
+			`YC-360 SCRIPT LOG DATA
 Is transmission completed: %t
 Resp: %s
 

internal/cli/cli.go

@@ -30,7 +30,7 @@ func Run() {
 	runCaptureModeIfConditionSatisfied()
 
 	if config.GlobalConfig.ShowVersion {
-		logger.Log("yc agent version: " + executils.SCRIPT_VERSION)
+		logger.Log("yc-360 script version: " + executils.SCRIPT_VERSION)
 		return
 	}
 
@@ -45,7 +45,7 @@ func Run() {
 		logger.Log("Error: %s", err.Error())
 	}
 
-	logger.Log("Agent is shutting down...")
+	logger.Log("yc-360 script is shutting down...")
 	agent.Shutdown()
 
 	if err != nil {