About PsychicMushroom

PsychicMushroom · ‎10-11-2024

Thanks for the reply. Cheers.

PsychicMushroom · ‎10-07-2024

Hi guys, Does anyone know even with the Trial version of Splunk Observability Cloud whether it still accepts logs being sent to it directly by the Splunk Otel Collector? According to this page : https://docs.splunk.com/observability/en/gdi/opentelemetry/components/splunk-hec-exporter.html , it says: "Caution - Splunk Log Observer is no longer available for new users. You can continue to use Log Observer if you already have an entitlement." As I'm using the Trial version, I'm just curious to see how Observability Cloud processes logs via fluentd, rather than use Log Observer Connect which uses the Universal Forwarder to send logs to Splunk Cloud/Enterprise first, and then Observability Cloud just views log events via the integration. Seems that Observability Cloud is not showing the ordinary syslog or windows events which get sent to it automatically out of the box by the Splunk Otel Collector. Tried setting up my own log file, but nothing shows up in O11y either.

PsychicMushroom · ‎07-24-2023

Hi, I heard through the grapevine that APM agent can now connect directly to ThousandEyes. Is this true? And is there any instructional documentation that shows how to configure the agents to achieve it ?

PsychicMushroom · ‎07-15-2023

This is the solution that worked for me .... Ensure entry in /etc/hosts containing the EC hostname as I'm installing the Event Service locally. platform-admin.sh stop-platform-admin Edit <platform_home>/mysql/db.cnf and made the following change: From: user=root To: user=appd Change the ownership of all the files in the EC home directory. chown -R appd:appd /opt/appdynamics platform-admin.sh start-platform-admin Remove the Events Service, and then deploy it again locally to the EC host. Events Service started OK.

PsychicMushroom · ‎07-11-2023

Hi Ryan, I'm also seeing this same error when installing Event Service locally on the Enterprise Console host (centos 8 stream). I installed the EC using platform-setup-x64-linux-23.4.0.10041.sh The appdynamics-events-service-cluster.log shows the below: [root@centos8stream logs]# cat appdynamics-events-service-cluster.log [2023-07-11T03:26:32,998][WARN ][o.e.c.l.LogConfigurator ] [centos8stream.localdomain] Some logging configurations have %marker but don't have %node_name. We will automatically add %node_name to the pattern to ease the migration for users who customize log4j2.properties but will stop this behavior in 7.0. You should manually replace `%node_name` with `[%node_name]%marker ` in these locations: /opt/appdynamics/platform/product/events-service/processor/elasticsearch/config/log4j2.properties [2023-07-11T03:26:33,179][ERROR][o.e.b.Elasticsearch ] [centos8stream.localdomain] fatal exception while booting Elasticsearch java.lang.RuntimeException: can not run elasticsearch as root at org.elasticsearch.bootstrap.Elasticsearch.initializeNatives(Elasticsearch.java:260) ~[elasticsearch-8.5.3.jar:?] at org.elasticsearch.bootstrap.Elasticsearch.initPhase2(Elasticsearch.java:166) ~[elasticsearch-8.5.3.jar:?] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:66) ~[elasticsearch-8.5.3.jar:?] Checking "netstat -an", port 9080 is not showing - no surprises there. Also note that " /opt/appdynamics/platform/platform-admin/bin/platform-admin.sh start-platform-admin" must be run as root user, otherwise it returns the error: [appd@centos8stream appdynamics]$ /opt/appdynamics/platform/platform-admin/bin/platform-admin.sh start-platform-admin Enterprise Console must be operated with user 'root'. Current user is appd

PsychicMushroom · ‎05-31-2023

Hi Guys, We are running AKS with CNI plugin with Synthetic Sever(Azure VM) and getting the below errors in the Chrome pod logs. Private Synthetic Agent version is 22.9.0 It's as though Chrome pod is unable to authenticate with heimdall, hence the 401 error. Has anyone seen this before? Not sure how to deal with this issue. INFO 2023-05-31 04:32:59,176 ad.internal idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 Creating directory: ../temp/customScreencasts INFO 2023-05-31 04:32:59,176 ad.internal idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 Creating directory: ../temp/pageScreencasts INFO 2023-05-31 04:32:59,176 ad.internal.HeimdallClient idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 Fetching measurement for id: 4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 ERROR 2023-05-31 04:32:59,188 ad.internal.HeimdallClient idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 Fetching measurement for id: 4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 failed Received status code: 401. Time taken for api call in ms: 0 ERROR 2023-05-31 04:32:59,189 ad.internal idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 Fetching measurement for id: 4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 failed Received status code: 401. Time taken for api call in ms: 0 Traceback (most recent call last): File "driver.py", line 79, in <module> measurement_data = heimdall_client.fetchMeasurement(MEASUREMENT_ID) File "/app/agent/Client/heimdall_client.py", line 73, in fetchMeasurement raise HeimdallClientException(errorMessage) customExceptions.HeimdallClientException: Fetching measurement for id: 4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 failed Received status code: 401. Time taken for api call in ms: 0 INFO 2023-05-31 04:32:59,189 ad.internal.ResultsUploader idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 Uploading artifacts

PsychicMushroom · ‎05-17-2023

Can anyone tell me if we enable SAML authentication on our on prem windows controller that we are still able to login to the controller using local accounts ? The concern is once SAML is configured and you logout and you can no longer login using a local account, how do we revert back to the "Authentication Provider" : Appdynamics in which uses local accounts? This tells me that you need to have 2 browser sessions open when configuring SAML: 1st session to be logged in as an Owner role and the 2nd session to enable SAML. If the 2nd session fails to login as SAML based user, then in the 1st session we have the ability to set "Authentication Provider" as Appdynamics again. This is to avoid locking out ourselves completely.

PsychicMushroom · ‎03-19-2023

Found it .... C:\AppDynamics\Platform\product\controller\appserver\glassfish\domains\domain1\appagent\conf

PsychicMushroom · ‎03-16-2023

Hi Guys, We have a Windows Controller and recently upgraded it and have end to end SSL from the BigIP F5 to the Controller working. When we log into the admin console (ie. admin.jsp) and back into the normal Controller UI, the Tier "App Server" doesn't show the node. Does anyone know the path location of the java agent is on the windows controller?

PsychicMushroom · ‎06-06-2022

Hi, Has anyone tried using the node.js agent to see if it will work with detecting the Next.js framework? Next.js is an open-source web development framework built on top of Node.js, so don't know if it will at least partially work.🐵

Posts	10
Solutions	1
Karma Given	0
Karma Received	4
Member Since	‎10-03-2024

Online Status	Offline
Date Last Visited	2 weeks ago

Does Observability Cloud still accept logs being s...

APM agents connecting directly to ThousandEyes ?

Chrome pod 401 error when running Private Syntheti...

SAML - can local AppD accounts still be used if SA...

Self Monitoring of the controller - location of th...

Next.js support?

Re: Does Observability Cloud still accept logs bei...