I get an alert like this everytime I create / delete a documentDB instance. I do not remember how did I set it up. I checked documentDB console as well as cloudwatch console, but can not see any relveant entry.
Event Source : db-instance
Identifier Link: https://console.aws.amazon.com/docdb/home?region=us-east-1#dbinstance:id=docdb-2019-08-30-10-48-09
SourceId: docdb-2019-08-30-10-48-09
Notification time : 2019-08-30 10:58:10.508
Message : DB instance created
Event ID : https://docs.aws.amazon.com/amazondocdb/latest/developerguide/events.html#RDS-EVENT-0005
Anyone can guide me how to get a notification like this for documentDB instances?
This is RDS instance alert created in cloudwatch - Events - Rules.
If you have created the alert as a "root" user, you can not view / modify it using IAM user who usually has limited privileges!
Related
I have integrated Elastic APM to my Vue.js App accordingly to the documentation (https://www.elastic.co/guide/en/apm/agent/rum-js/current/vue-integration.html)
In addition to the default events page-load and route-change I want to add custom transactions/spans for some button clicks.
I am stucked with checking if there is already an existing transaction start which I could use to add a custom span:
const transaction = this.$apm.currentTransaction()
transaction.startSpan('custom_span', 'type_name');
transaction.end();
However getting the current transaction fails (first line).
The Elastic RUM agent has support for click user interactions, therefore you shouldn't need to manually start these type of transactions.
Regarding the failure in your code the correct API call is getCurrentTransaction and not currentTransaction.
Hope this helps.
How can I get cloudwatch to send me the project tag of the ec2?
I have a cloudwatch rule that notify me when an ec2 state changes (stop/start).
Right now the alerts is emailing the ec2 current state and instanceId.
{"ec2state": "running"}
{"ec2id": "i-someEc2Id"}
How can I get cloudwatch to also send me the project tag of the ec2?
{"instance":"$.detail.instance-id","state":"$.detail.state"}
{"ec2state": "running"}
{"ec2id": "i-someEc2Id"}
{"ec2project": "projectname"}
This is not possible.
Instead, you will need to write code that takes the Instance ID and then calls DescribeInstance() to obtain details about the instance, including tags.
I am trying to create an alert in OMS when a Linux service is stopped.
AFAIK we have below options to accomplish your requirement.
Option I:
If the service/deamon is configured by default configurations then the service log information would be logged under /var/log/messages.
Whenever a Linux service is stopped if the information is getting logged in /var/log/messages file then follow below steps to get alerted:
Goto Azure portal -> YOURLOGANALYTICSWORKSPACE -> Advanced settings -> Data -> Syslog -> type 'daemon' -> click '+' -> click 'save'. For more information, refer this https://learn.microsoft.com/en-us/azure/azure-monitor/platform/data-sources-syslog link.
Goto Azure portal -> YOURLOGANALYTICSWORKSPACE -> Logs -> type 'Syslog' -> click 'Run'. Check 'SyslogMessage' column in the output. Output also have various other useful columns like SeverityLevel, ProcessName and ProcessID which you may use while developing the query based on your need.
So query would look something like shown below.
Syslog | where (Facility == "daemon") | where (SyslogMessage has
"xxxxxxx" and SyslogMessage has "stopping") | summarize
AggregatedValue= any(SyslogMessage) by Computer, bin(TimeGenerated,
30s)
Create and configure custom log alert in the Log Analytics workspace alert tile by using above query. Set the threshold value, frequency, period details while configuring an alert. Provide intended action group to get notified on alert getting triggered.
Option II:
If the service/deamon is custom configured then the service log information would be logged in that particular custom path.
Whenever a Linux service is stopped if the information is getting logged in /xxxx/yyyy/zzzz.txt file (or other examples are /aaaa/bbbb/jenkins/jenkins.log, cccc/dddd/tomcat/catalina.out, etc.) then follow below steps to get alerted:
Goto Azure portal -> YOURLOGANALYTICSWORKSPACE -> Advanced settings -> Data -> Custom Logs -> click 'Add +' -> .... For more information, please refer this https://learn.microsoft.com/en-us/azure/azure-monitor/platform/data-sources-custom-logs link.
Goto Azure portal -> YOURLOGANALYTICSWORKSPACE -> Logs -> type 'CUSTOMLOGNAME_CL' -> click 'Run'. Check something like 'RawData' column in the output.
So query would look something like shown below.
CUSTOMLOGNAME_CL | where (RawData has "xxxxxxx" and RawData has
"stopping") | summarize AggregatedValue= any(RawData) by Computer,
bin(TimeGenerated, 30s)
Create and configure custom log alert in the Log Analytics workspace alert tile by using above query. Set the threshold value, frequency, period details while configuring an alert. Provide intended action group to get notified on alert getting triggered.
Option III:
In case your service log data can't be collected with custom logs also then send the data directly to Azure monitor using HTTP Data Collector API that is explained here -> https://learn.microsoft.com/en-us/azure/azure-monitor/platform/data-collector-api.
An example using runbooks in Azure Automation is provided in Collect log data in Azure Monitor with an Azure Automation runbook is explained here -> https://learn.microsoft.com/en-us/azure/azure-monitor/platform/runbook-datacollect.
Hope this helps!! Cheers!! :)
I`m trying to modify RDS DB Instance launched in vpc by AWS API using ModifyDBInstance action. I`m not change instance type (instance launched with db.m1.small type and not canged), but I`m reciving message:
AWS Error. Request ModifyDBInstance failed. Cannot modify the instance class because there are no instances of the requested class available in the current instance's availability zone. Please try your request again at a later time. (RequestID: xxx).
According to AWS docs
To determine the instance classes that are available for a particular DB engine, use the DescribeOrderableDBInstanceOptions action. Note that not all instance classes are available in all regions for all DB engines.
So I have two quastions:
Is it possible to get by API only Instance types available in specific AZ? In DescribeOrderableDBInstanceOptions actions responce I have many instance types, which not available. I`m also checked responce of DescribeReservedDBInstancesOfferings action, and it`s doesn`t fit.
Why it possible to launch DBInstance with some instance type, but have troubles on trying to modify it DBInstance without changing instance type?
Any ideas?
It looks like one of the return values listed in this AWS RDS CLI call is AvailabilityZones
AvailabilityZones -> (list)
A list of Availability Zones for the orderable DB instance.
(structure)
Contains Availability Zone information.
This data type is used as an element in the following data type:
OrderableDBInstanceOption
Name -> (string)
The name of the availability zone.
Generally the CLI allows your to filter but it is not support for rds for some reason or another.
--filters (list)
This parameter is not currently supported.
The API returns the object OrderableDBInstanceOption which also has the AZ listed.
To answer #2 is that AWS does have capacity issues from time to time, like any other cloud or service provider, they are generally better at handling it than others. What AZ are you trying to use and size of instance? If you continue to have issues I would open a support ticket with AWS.
The easiest way is to select any one of the Rds instance you have in your infrastructure and click on Modify and there will be one option like dbInstanceTypes it is like drop down where you can find available instance types available in the particular region.
I’m using the rest api to create an envelope, and then configure it using the api sender view call (/restapi/v2/accounts//envelopes//views/sender) to get the DocuSign UI. Creating the envelope and viewing it the first time using sender view to bring up the docusign api works fine.
The problem occurs if instead of sending the envelope I click ‘save as draft’. When I try to go back to the envelope and view it again using sender view I get the following error with http status of 400:
{
"errorCode": "EDIT_LOCK_ENVELOPE_LOCKED",
"message": "The envelope is locked. The lock must be released before requesting the sender token for envelope, id = xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx."
}
The lock seems to wear off after time (apprx 20 mins). However after it wears off I can only view the item once, and then the lock is reapplied. This error only happens on my demo account but not on production, so it seems like it's an account setting, but I can't figure out what/where the setting is.
We have a bug logged on our side where Save Draft isn't correctly
releasing the lock on the envelope. We should have a fix for this issue
in our DEMO environment soon. The locking feature is currently only "ON"
in our DEMO environment but not in our Production environments while we
find and fix potential issues such as the one identified here. More
information about locking is in our February service pack (PDF) release
notes available here: https://www.docusign.com/support/releases.