UptimeRobot Raised Pricing by ~62% Any one got Email?

Comments

• slima4 Member

  October 19

  @cochon said:

  @slima4 said:
  all three shipped. _dmarc and other underscore names work, passkeys save in bitwarden...

  Ah that also seems to have solved my problem with passkeys not saving to YubiKeys, was finding the e-mail OTP method mildly annoying.

  glad it works, no more email codes for you
• slima4 Member

  October 19

  @JohnFilch123 said:
  @slima4 question - for some reason, when I add dns monitor or tls, I only see latency charts and nothing else. Am I supposed to see tls expiry dates and actual dns records for those types of monitoring?

  you were right, it was missing. fixed, monitor page now shows cert expiry, issuer and the current dns records

  Thanked by 1JohnFilch123
• Plioser Member

  October 19

  thanks. wildcards work now. group that fails as one is a good idea, noted, will ping you when it ships

  Thanks!!
• JohnFilch123 Member

  October 20

  @slima4 said: fixed

  Now clickhouse is eating resources very actively. I just had around 80% CPU usage and db size was like 30Gb. Redeploying helped, now size is 150MB but it is constantly increasing. CPU is between 4%-15%.

  Thanked by 1slima4
• slima4 Member

  October 20

  @JohnFilch123 said:

  @slima4 said: fixed

  Now clickhouse is eating resources very actively. I just had around 80% CPU usage and db size was like 30Gb. Redeploying helped, now size is 150MB but it is constantly increasing. CPU is between 4%-15%.

  its clickhouse system logs, they grow forever and eat cpu even at idle: https://github.com/ClickHouse/ClickHouse/issues/60016
  my bad, prod turns them off but the self host compose doesnt: https://github.com/uptimepage/uptimepage/issues/210
  until its fixed, disable them all, save this as ch-nologs.xml next to docker-compose.yml:

  <clickhouse>
      <asynchronous_metrics_update_period_s>60</asynchronous_metrics_update_period_s>
      <asynchronous_metric_log remove="1"/>
      <asynchronous_insert_log remove="1"/>
      <metric_log remove="1"/>
      <trace_log remove="1"/>
      <text_log remove="1"/>
      <query_log remove="1"/>
      <query_thread_log remove="1"/>
      <query_metric_log remove="1"/>
      <query_views_log remove="1"/>
      <part_log remove="1"/>
      <session_log remove="1"/>
      <error_log remove="1"/>
      <latency_log remove="1"/>
      <processors_profile_log remove="1"/>
      <opentelemetry_span_log remove="1"/>
      <background_schedule_pool_log remove="1"/>
  </clickhouse>
  

  then add under clickhouse volumes and restart:

  • ./ch-nologs.xml:/etc/clickhouse-server/config.d/nologs.xml:ro

  Thanked by 1JohnFilch123
• LEBUserJoe Member

  October 20

  @slima4 said:

  @JohnFilch123 said:

  @slima4 said: fixed

  Now clickhouse is eating resources very actively. I just had around 80% CPU usage and db size was like 30Gb. Redeploying helped, now size is 150MB but it is constantly increasing. CPU is between 4%-15%.

  its clickhouse system logs, they grow forever and eat cpu even at idle: https://github.com/ClickHouse/ClickHouse/issues/60016
  my bad, prod turns them off but the self host compose doesnt: https://github.com/uptimepage/uptimepage/issues/210
  until its fixed, disable them all, save this as ch-nologs.xml next to docker-compose.yml:

  <clickhouse>
      <asynchronous_metrics_update_period_s>60</asynchronous_metrics_update_period_s>
      <asynchronous_metric_log remove="1"/>
      <asynchronous_insert_log remove="1"/>
      <metric_log remove="1"/>
      <trace_log remove="1"/>
      <text_log remove="1"/>
      <query_log remove="1"/>
      <query_thread_log remove="1"/>
      <query_metric_log remove="1"/>
      <query_views_log remove="1"/>
      <part_log remove="1"/>
      <session_log remove="1"/>
      <error_log remove="1"/>
      <latency_log remove="1"/>
      <processors_profile_log remove="1"/>
      <opentelemetry_span_log remove="1"/>
      <background_schedule_pool_log remove="1"/>
  </clickhouse>
  

  then add under clickhouse volumes and restart:

  • ./ch-nologs.xml:/etc/clickhouse-server/config.d/nologs.xml:ro

  stop vibe coding

  Thanked by 1forest
• JasonM Member

  October 21

  @shiyi99 said: The part that bothers me most isn't the increase itself, it's the automatic bump at renewal with no new features attached — $96 to $156 a year is a big jump to swallow silently. Before paying it, I'd audit how many monitors actually need 30-second checks versus 5-minute ones;

  yeah extactly. if there a no new useful features why pay $156/yr for a $96 service!!!
• JohnFilch123 Member

  October 21

  @LEBUserJoe said:

  @slima4 said:

  @JohnFilch123 said:

  @slima4 said: fixed

  Now clickhouse is eating resources very actively. I just had around 80% CPU usage and db size was like 30Gb. Redeploying helped, now size is 150MB but it is constantly increasing. CPU is between 4%-15%.

  its clickhouse system logs, they grow forever and eat cpu even at idle: https://github.com/ClickHouse/ClickHouse/issues/60016
  my bad, prod turns them off but the self host compose doesnt: https://github.com/uptimepage/uptimepage/issues/210
  until its fixed, disable them all, save this as ch-nologs.xml next to docker-compose.yml:

  <clickhouse>
      <asynchronous_metrics_update_period_s>60</asynchronous_metrics_update_period_s>
      <asynchronous_metric_log remove="1"/>
      <asynchronous_insert_log remove="1"/>
      <metric_log remove="1"/>
      <trace_log remove="1"/>
      <text_log remove="1"/>
      <query_log remove="1"/>
      <query_thread_log remove="1"/>
      <query_metric_log remove="1"/>
      <query_views_log remove="1"/>
      <part_log remove="1"/>
      <session_log remove="1"/>
      <error_log remove="1"/>
      <latency_log remove="1"/>
      <processors_profile_log remove="1"/>
      <opentelemetry_span_log remove="1"/>
      <background_schedule_pool_log remove="1"/>
  </clickhouse>
  

  then add under clickhouse volumes and restart:

  • ./ch-nologs.xml:/etc/clickhouse-server/config.d/nologs.xml:ro

  stop vibe coding

  Ok