Hi @Ryan.Paredez , Yes, I checked the reply from Rajesh, thank you! Glad to know that my feedback helps to do a minor contribution to the community. Hope you have a great day too! Regards Gustav...
See more...
Hi @Ryan.Paredez , Yes, I checked the reply from Rajesh, thank you! Glad to know that my feedback helps to do a minor contribution to the community. Hope you have a great day too! Regards Gustavo Marconi
Hello @Gustavo.Marconi ,
By default SaaS controller is SSL enabled but I see the error message is "http". Could you please check your config if you have provided http or https.
[ERROR]: 2024-07-...
See more...
Hello @Gustavo.Marconi ,
By default SaaS controller is SSL enabled but I see the error message is "http". Could you please check your config if you have provided http or https.
[ERROR]: 2024-07-08 16:17:58 - agentregistrationmodule.go:131 - Failed to send agent registration request: Post "http://pracso-nfr.saas.appdynamics.com:443/sim/v2/agent/clusterRegistration": EOF
1. Now ssh into your appdynamics-operator pod or cluster agent pod kubectl -n <namespace> exec -it <appdynamics-operator-pod> -- /bin/sh
2 . Run the following command and send us the output for this:
curl -v -k -u singularity-agent@tatadigital:<access_key> https: // pracso-nfr.saas.appdynamics.com.com:443/sim/v2/agent/clusterRegistration
Hope this will figure it out what is the cause. Keep us posted.
Best Regards, Rajesh Ganapavarapu
Hi @Rajesh.Ganapavarapu , I applied the command: kubectl get secret cluster-agent-secret -n appdynamics -o jsonpath='{.data.controller-key}' | base64 --decode And it replies me with my controller...
See more...
Hi @Rajesh.Ganapavarapu , I applied the command: kubectl get secret cluster-agent-secret -n appdynamics -o jsonpath='{.data.controller-key}' | base64 --decode And it replies me with my controller-key. The agent version that I'm using is 24.6.0-481, appdynamics-cluster-agent-alpine_linux_amd64-24.6.0.481.zip was the version that I downloaded. In the cluster-agent.yaml the image is set to: "docker.io/appdynamics/cluster-agent:latest". I re-deployed everything and check again the logs for the cluster-agent, it shows me this: root@ubuntu-k8s-test:/home/gmarconi/appdynamics/cluster-agent# microk8s kubectl logs -n appdynamics k8s-cluster-agent-df58dfdc5-wtl7b CA_PROPERTIES= -appdynamics.agent.accountName=pracso-nfr -appdynamics.controller.hostName=pracso-nfr.saas.appdynamics.com -appdynamics.controller.port=443 -appdynamics.controller.ssl.enabled=false -appdynamics.agent.monitoredNamespaces="default" -appdynamics.agent.event.upload.interval=10 -appdynamics.docker.container.registration.interval=120 -appdynamics.agent.httpClient.timeout.interval=30 APPDYNAMICS_AGENT_CLUSTER_NAME=Tasks-Webapp [ERROR]: 2024-07-08 16:17:58 - secretconfig.go:68 - Problem With Getting /opt/appdynamics/cluster-agent/secret-volume/api-user Secret: open /opt/appdynamics/cluster-agent/secret-volume/api-user: no such file or directory [INFO]: 2024-07-08 16:17:58 - main.go:57 - check env variables and enable profiling if needed [INFO]: 2024-07-08 16:17:58 - agentprofiler.go:22 - Cluster Agent Profiling not enabled! [INFO]: 2024-07-08 16:17:58 - main.go:60 - Starting APPDYNAMICS CLUSTER AGENT version 24.6.0-481 [INFO]: 2024-07-08 16:17:58 - main.go:61 - Go lang version: go1.22.3 W0708 16:17:58.556623 8 client_config.go:618] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. [INFO]: 2024-07-08 16:17:58 - main.go:78 - Kubernetes version: v1.29.4 [INFO]: 2024-07-08 16:17:58 - main.go:236 - Registering cluster agent with controller host : pracso-nfr.saas.appdynamics.com controller port : 443 account name : pracso-nfr [WARNING]: 2024-07-08 16:17:58 - agentregistrationmodule.go:359 - "default" is not a valid namespace in your kubernetes cluster [INFO]: 2024-07-08 16:17:58 - agentregistrationmodule.go:363 - Established connection to Kubernetes API [INFO]: 2024-07-08 16:17:58 - agentregistrationmodule.go:68 - Cluster name: Tasks-Webapp [INFO]: 2024-07-08 16:17:58 - agentregistrationmodule.go:119 - Initial Agent registration [ERROR]: 2024-07-08 16:17:58 - agentregistrationmodule.go:131 - Failed to send agent registration request: Post "http://pracso-nfr.saas.appdynamics.com:443/sim/v2/agent/clusterRegistration": EOF Noticed that -appdynamics.controller.ssl.enabled is set to false, but I don't know how to set it to true, also not sure if that's the problem. Hope you can help me Rajesh. Have a great day! Regards Gustavo Marconi
I made changes, but I can't manage to change the color.
index="db_pci_mssqlatom" sourcetype=*
| dedup 1 _raw
| top trans_status showperc=0
| transpose 0 header_field=trans_status
| search colum...
See more...
I made changes, but I can't manage to change the color.
index="db_pci_mssqlatom" sourcetype=*
| dedup 1 _raw
| top trans_status showperc=0
| transpose 0 header_field=trans_status
| search column="count"
Regex does not convert the epoch time, but it can extract the time for further conversion. If those logs are taken from a single log file, then Splunk will by default put each line in a separate eve...
See more...
Regex does not convert the epoch time, but it can extract the time for further conversion. If those logs are taken from a single log file, then Splunk will by default put each line in a separate event and most likely guess the epoch as the timestamp. Then the timestamp (_time) will be human-readable in the event view, or it can be made human-readable using ctime()
Is there a Regex to convert the epoch to human readable time upon ingestion ? [1720450799] Error: Got check result for service 'CPU Usage' on host. [1720450799] Error: Got check result for se...
See more...
Is there a Regex to convert the epoch to human readable time upon ingestion ? [1720450799] Error: Got check result for service 'CPU Usage' on host. [1720450799] Error: Got check result for service 'Disk Usage var' on host. [1720450799] Error: Got check result for service 'Disk Usage opt' on host.
The UF will log communication failures in splunkd.log. Yes, you can monitor the indexers for no logs from hosts. There are apps, including TrackMe, that can help with that.
If the host cannot reach the indexer then there will be nothing logged on the indexer to monitor. The UF will log any failures to connect so that is the place to check, but you will have to do that ...
See more...
If the host cannot reach the indexer then there will be nothing logged on the indexer to monitor. The UF will log any failures to connect so that is the place to check, but you will have to do that on the host rather than in Splunk.
Hello @Ayodele.Akingbulu,
Thanks for asking your question on the community. It's been a few days with no reply. Have you found a solution yourself or anything new you can share? If you are still...
See more...
Hello @Ayodele.Akingbulu,
Thanks for asking your question on the community. It's been a few days with no reply. Have you found a solution yourself or anything new you can share? If you are still looking for help, I found this AppDynamics Documentation: https://docs.appdynamics.com/appd/24.x/24.6/en/cisco-appdynamics-essentials/dashboards-and-reports/dash-studio/thousandeyes-integration-with-cisco-appdynamics
Additionally, you can also contact Cisco AppDynamics Support for more help. https://www.appdynamics.com/support
Hi @Gustavo.Marconi,
Have you had a chance to check out the reply from @Rajesh.Ganapavarapu? I wanted to let you know I have also contacted the Docs team and shared your feedback regarding the docu...
See more...
Hi @Gustavo.Marconi,
Have you had a chance to check out the reply from @Rajesh.Ganapavarapu? I wanted to let you know I have also contacted the Docs team and shared your feedback regarding the documentation.
That's my mistake, I had selected the wrong app when I made the post. I've now updated the OP to the correct app in question - https://splunkbase.splunk.com/app/5433 I'm confused myself, I'm not see...
See more...
That's my mistake, I had selected the wrong app when I made the post. I've now updated the OP to the correct app in question - https://splunkbase.splunk.com/app/5433 I'm confused myself, I'm not seeing anything that points to an api issue in the logs. The only thing is that this is a relatively new api endpoint for the app and may not have had all the kinks ironed out.
Hi @Meri.jaan,
Thanks for asking your question on the Community. I know it's been a few days and the community has not jumped in to help.
Have you been able to find a solution or anything you ca...
See more...
Hi @Meri.jaan,
Thanks for asking your question on the Community. I know it's been a few days and the community has not jumped in to help.
Have you been able to find a solution or anything you can share? I noticed you shared documentation to a slightly older version of AppD Documentation. Here is the one that relates to your AppDynamics version: https://docs.appdynamics.com/appd/24.x/latest/en/application-monitoring/configure-instrumentation/transaction-detection-rules/message-queue-entry-points