วีดีโอ

@@techjadoo742 endpoints monitorong you waana do ?

@@techontarget yes , for laptops of developers WFH and aws infra, main moto to clear SOC2 audit

@@techjadoo742 bro am not sure about this, will look into this, thanks

@@Kk-rl7nv sure

thanks buddy i will look for it, can you pls support us to share video with your network like linkdin if possible.

@@gthirupathi8739 not yet

@@techontarget please do it will usefull

@@srivarshithabobby7499 hi where you exactly got the error at which step

@@MightyMike55 what happened bro

@@RahulKumar-et3rm might be issie in your ibstallation

@@PathanTausifkhan-jf7pp not currently but will look for it.

Thanks for the update when selected time area like any time filter select after export this data there is not match data in sheet above which time selected

@@ShivamBhamare-lk1ww there might be configuration mismatch, you have validate it. You can match your configuration with the video

@@gthirupathi8739 that can be done

@@techontarget video is there ha? Can you please share that video.

@@gthirupathi8739 no videp is not there but you can look into official doc

@@techontarget yes i gone through official docc. But archiving data to mont s3 not given proper way. Wazuh cloud service they provided clear docs.

@@gthirupathi8739 ok, i will also look into it when i got free

@@gthirupathi8739 in official doc it might be there, can you explore. Let me also check

@@Vostro123 it very straightforward as you seen in video, might be some internal restriction by your organization.

@@gthirupathi8739 either server not up or connection bet server to dashboard is broken

@@techontarget all services runing fine. Local host ip I given

I can look on this eith you on ths weekend

@@techontarget yeah its resolved thanks

@@gthirupathi8739 would you like to share how you resolve it might help other visitor who came across.

Thanks for the visit

@@gthirupathi8739 yes you need certs again. Note is not clear

@@sourabhdeshpande2112 t2 large

@@stream.abhimanyu sry for that, will try to improve it.

Bikul dashboatd se bhi aage ja paoge

Puri playlist bna rkhi hai dashboard de aage ja kr module implement kriye

Thanks for kind words

I will try to improve in future video. Sry for inconveinence

Thanks

sir more videos create in devops engineer interview questions

@@KrishnaAdale sure

Thanks

You can follow above video for it, there are also some updation done, pls follow oficial doc too.

It is in wiki

Sry to hear that, try to improve my channel.

Can u tell bit more, in which part u find more difficulty, intro part or implementation part

Sure

Copy the woodle from official doc

@@techontarget thanks a lot, your course helps me a lot

Thanks, currently i dont have that video but look for it

First of all thanks for your time and words. Second - Sry for some issues, you can watch same video in english language in our channel.

Above scenario will also work for you.

@@techontarget do you have a video where you set up mod security for wazuh agents?

@@sangngothanh89 mod ?

Sure, will look for that

Yes

@@techontarget thank you for reply, and for the education

Might b using wrong password, not sure

🙏🙏🙏🙏

Watch video 1 wazuh tutorial: th-cam.com/play/PLI0vJRMEGNYR1weBAL2zj8WmnodydFRiU.html

It should work, might be some changes happen in wazuh new version. Pls also follow official doc

Yes

Pls follow the official doc too

Will look around this

Its available in wazuh official doc

Sure will look for it

You might be missing some step

0 is for root only mean you login with root user

What issue you are facing

You're welcome!

Check channel bio

@@techontarget sir, meeting scheduled for tomorrow 5th May 2024- 3.00 pm

@@techontarget can we have a meeting today, ? I really need your help on this

@@techontarget can we have a meeting today? I really need your help on this

@@SandeepDash-sv6ql we already have schedule call

Diagnos more logs why its not coming up

Its connectiom to elasticsearch getting failed or sonething else issue.

@@techontarget sir can we connect with a good meet. Its quite important for me

​@@techontarget {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:xpack_main@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:graph@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:spaces@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:searchprofiler@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:ml@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:tilemap@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:watcher@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:grokdebugger@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:logstash@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:beats_management@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:maps@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:index_management@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:index_lifecycle_management@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:rollup@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:remote_clusters@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:cross_cluster_replication@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:42Z","tags":["status","plugin:snapshot_restore@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2024-05-04T04:44:45Z","tags":["reporting","browser-driver","warning"],"pid":1,"message":"Enabling the Chromium sandbox provides an additional layer of protection."} {"type":"log","@timestamp":"2024-05-04T04:44:45Z","tags":["reporting","warning"],"pid":1,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml"} {"type":"log","@timestamp":"2024-05-04T04:44:45Z","tags":["status","plugin:reporting@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from uninitialized to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2024-05-04T04:44:45Z","tags":["status","plugin:security@7.2.0","error"],"pid":1,"state":"red","message":"Status changed from green to red - [data] Elasticsearch cluster did not respond with license information.","prevState":"green","prevMsg":"Ready"} {"type":"error","@timestamp":"2024-05-04T04:45:12Z","tags":["warning","process"],"pid":1,"level":"error","error":{"message":"Error: Request Timeout after 30000ms at /usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:362:15 at Timeout.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:391:7) at ontimeout (timers.js:436:11) at tryOnTimeout (timers.js:300:5) at listOnTimeout (timers.js:263:5) at Timer.processTimers (timers.js:223:10)","name":"UnhandledPromiseRejectionWarning","stack":"UnhandledPromiseRejectionWarning: Error: Request Timeout after 30000ms at /usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:362:15 at Timeout.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:391:7) at ontimeout (timers.js:436:11) at tryOnTimeout (timers.js:300:5) at listOnTimeout (timers.js:263:5) at Timer.processTimers (timers.js:223:10) at emitWarning (internal/process/promises.js:81:15) at emitPromiseRejectionWarnings (internal/process/promises.js:120:9) at process._tickCallback (internal/process/next_tick.js:69:34)"},"message":"Error: Request Timeout after 30000ms at /usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:362:15 at Timeout.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:391:7) at ontimeout (timers.js:436:11) at tryOnTimeout (timers.js:300:5) at listOnTimeout (timers.js:263:5) at Timer.processTimers (timers.js:223:10)"} {"type":"error","@timestamp":"2024-05-04T04:45:12Z","tags":["warning","process"],"pid":1,"level":"error","error":{"message":"Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 127)","name":"UnhandledPromiseRejectionWarning","stack":"Error: Request Timeout after 30000ms at /usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:362:15 at Timeout.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:391:7) at ontimeout (timers.js:436:11) at tryOnTimeout (timers.js:300:5) at listOnTimeout (timers.js:263:5) at Timer.processTimers (timers.js:223:10)"},"message":"Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 127)"} {"type":"log","@timestamp":"2024-05-04T04:45:15Z","tags":["reporting","warning"],"pid":1,"message":"Reporting plugin self-check failed. Please check the Kibana Reporting settings. Error: Request Timeout after 30000ms"} {"type":"log","@timestamp":"2024-05-04T04:45:15Z","tags":["warning","task_manager"],"pid":1,"message":"PollError Request Timeout after 30000ms"} {"type":"log","@timestamp":"2024-05-04T04:45:15Z","tags":["warning","maps"],"pid":1,"message":"Error scheduling telemetry task, received NotInitialized: Tasks cannot be scheduled until after task manager is initialized!"}

@@SandeepDash-sv6ql is it new or existing setup

how wazuh is backdoor ?

Yes if you had followed the video, you will get logs ij aws module i made this two month back, no major changes happen from wazu.