I have zabbix on virtual machine Cent OS. Zabbix is configured to access only from the internal network https://192.168.42.13
Server Cent OS has access to the internet.
I download from Office365 MS Teams connector configuration for zabbix. Made all settings in zabbix, but did not get any notification in MS Teams.
Is this problem because zabbix is configured to access only the internal network? If yes, how make this notification without opening zabbix front end to the internet?
Mimic the same process that is followed to enable/send zabbix notifications to slack.
Enable an incoming webhook to your MS Teams channel.
Use that incoming webhook and creat Ms teams media type on your zabbix server. Mimic the javascript in slack media type, it should work
You didn't provide logs or information about error on that but I also had issues with teams webhook few weeks ago.
Last time microsoft changed URI for webhook and there is required small change in zabbix script for that (if you didn't do that yet).
Administration -> media type -> MS Teams -> script:
there you have to check if you have proper check:
if (!params.teams_endpoint) {
throw 'Cannot get teams_endpoint';
}
else if (!params.teams_endpoint.includes('office.com/webhook')) {
throw 'Invalid MS Teams webhook URL: ' + params.teams_endpoint;
}
that change in "else if" helped for me
Related
I created an ASP.NET Core Web API and deployed it in Azure as an App Service.
I created a Hybrid Connection and installed the Hybrid Connection Manager on the On-Premise Database Server, set the Hybrid Connection Status to Connected (Successfully connected the App Service with On-Premise Db Server).
When sending Get Request or accessing the Web API on the web browser or Postman
The Result I receive is:
500 - The request timed out. The web server failed to respond within
the specified time.
When developing the Web API on my local machine it works smoothly and I could connect to the On-Premise through a VPN connection.
I also added this piece of code
services.AddDbContext<RepositoryContext>(o => o.UseSqlServer(connectionString, sqlServerOptionsAction: sqlOptions =>
{
sqlOptions.EnableRetryOnFailure(
maxRetryCount: 5,
maxRetryDelay: TimeSpan.FromSeconds(60),
errorNumbersToAdd: null);
}));
In the absence of more information, the 500 error, I guess the most likely reason is that there is a problem connecting to the On-Premise sql server.
TroubleShooting:
Click Diagnose and solve problems to view Application Event Log to view specific logs.
(Optional) Open Application Logging (Filesystem) and Detailed error message.
Specifically, you can log in to the scm website to view the error log.
If you test the interface and connect to the database locally or using vpn, there is definitely no problem. Now the problem must be the database connection part. It is recommended to recheck Hybrid connections. You also can raise a support ticket on portal, let them check logs and help you.
Related Posts:
1. Hybrid Connection Shows “Connected”, but Application Fails to Connect
2. Azure Web App Hybrid Connection Failing
Problem
The Hybrid Connection's Endpoint/Host I made in Azure had a different name as the SQL server. I named the endpoint randomly instead of giving it the actual name/IP address.
Additional info
Even if you installed the Connection Manager on the Server and the Status is set to Connected, this doesn't mean that your App Service will communicate with the Database.
Solution
Create a new Hybrid Connection and set the Endpoint Host name with the actual name/IP address, where the Hybrid Connection Manager is installed.
I am using CO-TURN as my VoIP platform.
What I am looking for is that how can I get information about which users are in an ongoing voice call?
That depends on how you are creating sessions on turn server. You can check it from WebUi.
But your application server should manage all this not turn server as this is not role of turn server.
I am implementing push notifications for mobile banking application using GCM. According to IBM Document we have to open ports 5228,5229,5230 and 443. And our firewall should allow all the IP ranges specified in ASN15169 specification. Because of security reasons Security team not giving access to IP ranges of ASN15169. Please suggest me if we have any other way to access gcm services for application instead of allowing all the ip blocks.
This is related to Google.
If your banking environment does not allow these ports then you need to either convince the security managers of the bank to allow it. Or, create a separate network from the banking systems where you will install a server and connect a device to test the notifications.
I am very new to splunk and trying to set up domain account, but with the custom options the installation rollbacks. I want to receive data from remote system by a universal forwarder. I have provided the same port number as the receiving port which is forward data configurations in remote system. What am I missing here? Can I do so with local system installation?
same question is asked here ...
http://answers.splunk.com/answers/232340/why-am-i-unable-to-set-up-the-domain-account-for-s.html
but there is no answer..
Please help..
The service account must be entered as "domain.name\username" rather than just "username".
I experienced the same problem, having everything configured correctly for running the Universal Forwarder as a service account. However, I failed to enter the service account as "domain.name\username". Just specifying "username" does not work, either when running the installer interactively or silently.
I made an app that connect to server to get some info
I use HTTPAdapter to send a post request
It runs successfully with preview on my browser
I've check that tha adapter and code has no bug
but it failed when I run it on my virtual device(3G network)
Request timeout for [http://172.16.100.106:10080/WistronAppProject/apps/services/api/WistronApp/android/query]
why i can't send request with different ip domain ?
it has to run in the same network?
there is some other problem?
The device must be able to connect to the same network Worklight Server is in.
If your server does not have a PUBLIC IP address, meaning it is running for example in your office network that is not available outside, then your device MUST be connected to the same office network via WiFi. If you connect via 3G, it will not be able to find the Worklight Server and connect to it.